This section covers common issues when creating and running automations. The following troubleshooting topics are available:

Automation Doesn't Trigger — Why automations don't fire when expected
Run Fails with Guardrail Failure — Understanding and fixing guardrail violations
Agent0 Doesn't Call Expected Tools — Why Agent0 skips or can't access certain tools
Variables Show as {{...}} in Output — Why variables aren't resolving correctly
Missing Integration Warnings — Resolving integration connection issues

Run Status Meanings

When viewing run history, each run shows a status:

Success: Automation completed successfully. Review the summary and tool calls to see what Agent0 did.
Error: Automation encountered an error during execution. Check the error message and tool call failures.
Guardrail Failure: Automation violated guardrail constraints (e.g., required tool not called, timeout exceeded).
In Progress: Automation is currently running. Check back later or view live progress.
Cancelled: Automation was manually stopped or superseded by a newer run.

Limits

Timeout: Default is 10 minutes per run. Increase in guardrails for complex automations.
Concurrent runs: Controlled by concurrency policy (none, parallel, queue, skip, supersede).
Queue capacity: Queue policy holds up to 100 triggers. Additional triggers are discarded.
Tool limits: Each tool inherits limits from its integration (GitHub API rate limits, Slack rate limits, etc.).

Every automation run has a feedback option. Use it to report:

Feedback goes directly to the product team and helps prioritize improvements.

For urgent issues, contact your Dash0 account team.