> ## Documentation Index
> Fetch the complete documentation index at: https://bytebeam.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Action Timeout

## Overview

Action Timeout allows you to set a timeout period for actions on a device if they remain stuck in any state other than "Completed" or "Failed."

## Why Use Action Timeouts?

In certain situations, an action may get stuck in a particular state, preventing subsequent actions from executing. By setting an action timeout, you can mark these stuck actions as "Failed" to free up the device for future tasks.

![](https://usercontent.clueso.io/1f4455e0-789e-4beb-8cd9-4dac96bc47e4/ce5451ce-97b4-4427-bbc6-9c9407629c36/a08e682b-19f1-4823-a6e7-0ed5696922a3/images/e863c3a3-547a-4252-9d20-d888e3548065.gif)

## Timeout Configuration Options

Timeouts can be configured in three places:

**Action Types** - Specific to individual action types.

**Global Settings** - Applies to all action types.

**Advanced Settings** - Global for all action types but only affects actions in the "Scheduled" state.

## Action Types Timeout

Set timeouts for individual action types, applicable if they’re stuck in any state other than "Scheduled," "Failed," or "Completed."

To set a timeout for an action type:

**1. Access Settings Tab**

Navigate to the Settings tab by clicking on your username at the top right.

**2. Go to Action Types and Edit**

Go to [Action Types](https://bytebeam.io/docs/platform-guide/action-types/action-types) and click on the edit icon next to the action type you want to update.

**3. Set Timeout**

In the Timeout dropdown, select a duration from the list or set a custom time, then click Submit.

## Global Timeout

The global timeout applies to all action types that are stuck in any state other than "Scheduled," "Failed," or "Completed."

> [!NOTE]
>
> The default global timeout for new projects is set to 30 days.

To configure the global timeout:

**1. Access Settings Tab**

Navigate to the Settings tab by clicking on your username at the top right.

**2. Edit Global Timeout**

Go to the [General](https://bytebeam.io/docs/platform-guide/general-settings.md) tab, and click the edit icon next to Default Action Timeout.

**3. Set Timeout**

Select a duration from the Timeout dropdown, or set a custom time, then click the Save icon.

## Advanced Settings Timeout

This timeout applies globally to all action types but only affects actions that are stuck in the "Scheduled" state.

Use Case: If you have a phased action with a success-rate dependency, and a prior phase does not meet its criteria, the next phase may get stuck in "Scheduled." This timeout will help mark those phases as "Failed" to allow progression.

> [!NOTE]
>
> The default for scheduled actions is set to "Never".

To set a timeout for scheduled actions using Advanced Settings:

**1. Access Advanced Settings**

In the Advanced Settings section, enable the Advanced Settings Toggle.

**2. Set Timeout**

Choose a timeout value from the dropdown, or set a custom time, then trigger the action.

## Summary of Timeout Precedence

For actions stuck in any state other than "Scheduled," "Completed," or "Failed," the timeout is checked in this order:

1. Action Types Timeout (if configured)

2. Global Timeout (if action types timeout is not configured)

For actions in the "**Scheduled**" state, only the **Advanced Settings Timeout** applies, overriding any Action Types or Global timeouts.

This approach ensures that actions can proceed smoothly without getting indefinitely delayed in unresponsive states.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.