How-to
How to troubleshoot a failed run
When a run fails, open it from Executions to see exactly what went wrong — then fix and re-run. Here’s the flow.
- Open Executions and click the failed run (status FAILED or TIMEOUT).
- Read the error message and the per-step details — the failing step is marked, with its input, output, and any tools it called.
- Fix the cause in the agent or workflow (see common causes below).
- Click 🔁 Replay to re-run with the exact same input, and watch the fresh run.
Common causes
- Missing tool connection — e.g. Slack/Discord/Telegram/Notion not connected in Settings → Integrations.
- A tool call failed — check the “Tools used” details for the API’s response.
- TIMEOUT — a run stuck over 30 minutes is auto-marked TIMEOUT; simplify the step or check the LLM/provider.
- Bad LLM key — if using your own key (Account → BYO keys), confirm it’s valid.
Replay uses the workflow’s current definition, so fixing the workflow and replaying is the fastest way to confirm the fix.