Org Settings

Execution Limits

Control how far automated action chains can run in your org to prevent runaway processes.

# What is a chained action?

When an action runs, it can automatically trigger another action as part of a workflow. These are called chained actions. The following tasks produce chained actions:

• Send Action — sends an action to one or more stubs automatically after the current action completes.
• Create Stub with replay_action_on_created_stub: true — creates a new stub and immediately replays the current action on it.

In most cases this is intentional and useful. However, if a workflow is misconfigured, chained actions can trigger each other in a loop, causing processes to run indefinitely and consume unnecessary resources.

# Chained Action Count Limit

The Chained Action Count Limit lets you control how many times an action can be automatically triggered in a single chain before Stubber stops it.

Each time an action is triggered automatically by another action, a counter increments by one. If that counter exceeds the limit, the action is rejected and an error is recorded on the stub.

Note: This limit only applies to automatically triggered (chained) actions. Actions performed directly by a user are not affected.

# Setting the limit

The easiest way to set this is through the Org Settings page in your organization. Navigate to Org Settings, find the Execution Limits section, and enter your desired limit in the Chained action count limit field. Save the draft and publish it for the change to take effect.

Alternatively, if you are editing the _org template directly, ensure you have completed the steps for adding Org Settings, then add the following to your _org_settings object in the template data:

        {
  "_org_settings": {
    "execution": {
      "chained_action_count_limit": 25
    }
  }
}

      

After making changes, publish the _org template for them to take effect.