> ## Documentation Index
> Fetch the complete documentation index at: https://docs.letsflow.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot automations

> Investigate failed, waiting, or missing automation runs.

## Investigate a failed run

<Steps>
  <Step title="Open Automations → Monitoring.">
    Open **Automations → Monitoring**.
  </Step>

  <Step title="Filter to failed runs.">
    Choose the team and time range. Then select the **Failed or denied** chip. It shows both failed
    and denied runs.
  </Step>

  <Step title="Open the run.">
    Open the run actions and select **Open run**.
  </Step>

  <Step title="Review the failure.">
    Review the failing step, input summary, output, and diagnostic.
  </Step>

  <Step title="Check the connection.">
    Check the named connection when an external action failed.
  </Step>
</Steps>

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**.

## Related topics

* [Run history and debugging](/automations/run/run-history-and-debugging)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.