Automation Settings contains configuration options that govern how an automation runs at a global level.
Overview
Automation Settings contains configuration options that govern how an automation runs at a global level. These settings affect logging, execution priority and reliability across all nodes in the workflow, and are found in the automation's settings panel rather than on individual nodes.
Execution Tier
The Execution Tier setting controls the priority level at which the automation runs relative to other automations in the system. Higher tiers receive more processing resources and are prioritized in the execution queue.
Default Tier
All automations start on the default execution tier, which provides standard processing priority suitable for the majority of workloads.
Dynamic Tiers
Dynamic tiers allow the execution priority to vary per automation run based on request headers passed at trigger time. This enables a single automation definition to serve multiple priority levels — for example, serving premium customers at a higher tier than standard customers.
Field | Description |
|---|---|
Default Tier | The tier the automation runs on when no mapping matches. |
Header Key | The header to look for in the automation. You define one header key per automation. |
Mappings | Click Add Mapping to add a row for each header Value and the Tier it maps to. |
When the incoming header value matches a mapping, the run executes on that tier. Otherwise, the automation runs on the Default Tier.
Logging
Logging controls how much execution data gets captured and stored for each run.
Enable Logging
Stores execution data for runs of this automation. It is on by default. When you turn it off, runs are not recorded.
Capture depth
Choose how much data each run captures. Each level includes everything from the previous one.
Level | What it captures |
|---|---|
Run summary (default) | A high-level record for each run: trigger source and start time, success or failure status, and total execution duration. Good for audit trails and monitoring. |
Step details | Everything in Run summary, plus the execution status and time taken for each step. Use it to trace execution paths. |
Full trace | Everything in Step details, plus the input and output payloads of every step. Ideal for debugging, but it increases storage usage. |
Important: A lower capture depth leaves less data for debugging failed runs. Changes to Enable Logging and Capture depth apply only to future runs.
Log Level
Captures logs at and above the chosen severity level during execution: Error (default), Warn, Info, Debug or Trace.
Run Level Timeout
Automation runs time out after this period, in milliseconds.
Circuit Breaker Settings
The circuit breaker stops the automation from repeatedly making requests to a failing or unresponsive API. Turn it on and set thresholds such as Failure rate %, Slow call rate %, Sliding window type, Sliding window size and Wait duration in open state.
Telemetry Metrics
Define metrics to be consumed implicitly against this automation. Turn on the toggle, then add the metrics you want to record.
Runtime User Connections
Allows app connections to be swapped at run time during execution. This section appears only for callable automations that use apps which support it.
Notes
Keep the following in mind when using Automation Settings:
Choose the Execution Tier that matches the automation’s workload before deploying.
Saving settings creates a new draft version. Deploy the automation to apply the new settings to live runs; past runs are not affected.
Review Execution Tier options with your workspace administrator before assigning a high-priority tier to a non-critical automation.
Use Full trace only where you need payload data for debugging, since it increases storage usage.