Skip to main content

​
Investigate a failed run

1

Open Automations → Monitoring.

Open Automations → Monitoring.
2

Filter to failed runs.

Choose the team and time range. Then select the Failed or denied chip. It shows both failed and denied runs.
3

Open the run.

Open the run actions and select Open run.
4

Review the failure.

Review the failing step, input summary, output, and diagnostic.
5

Check the connection.

Check the named connection when an external action failed.
Fix the cause before rerunning. A rerun is new work and can repeat changes in the connected system.

​
A run is waiting

  • Check My approvals on Home, or the run’s linked request, when a decision is pending.
  • Check the run log for missing input or another blocker.
  • For a connection failure, repair the connection before rerunning.

​
A trigger did not run

Open Automations → Triggers and check its status, last activity, and last run.
  • For a schedule, check the next run time.
  • For an event, check whether it was seen, matched, or dispatched.
  • Open the automation when the trigger shows an error.
If the trigger looks healthy but no run exists, report the automation name, team, expected time, and trigger type through Feedback.