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

# Monitor automations

> Check automation health, find a run, and open its detailed history.

## Monitoring views

Choose a view for the question you need to answer:

| View | Use it for |
| - | - |
| **Automations → Monitoring** | Active runs, recent failures, blockers, and run history for a selected team or All teams |
| **Analytics → Dashboard** | Aggregate production-run success for the selected teams and period |
| **Run history** in an automation | Run history for that automation |

Access follows your organization and team role. Monitoring includes production and test runs.
Analytics excludes test and active runs from its success-rate denominator, so its totals can differ from Monitoring.

## Check automation health

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

  <Step title="Choose a team or All teams." />

  <Step title="Set the time range." />

  <Step title="Review the status totals, success rate, failures, and blockers." />

  <Step title="Use the status chips and filters to narrow Recent runs." />

  <Step title="Open a run's actions and select Open run." />
</Steps>

## Find runs

Monitoring includes active runs of any age and finished runs with activity in the selected time
range. Its status categories account for Total. Pending includes requested and queued runs.
The Active filter includes pending, running, waiting, and cancellation requests.

Recent runs shows ten runs per page. Active runs appear first, followed by recent finished runs.
Use **Next** and **Previous** to browse every run in the selected scope and time range.

Search by run key (such as `RUN-123`), run ID, automation, ticket title, ticket key, or team.
Search ignores letter case and puts an exact run key match first.
Select a row's run key to open it when you have source access.

Search and filters cover all matching runs. The count shows the filtered total; the page range
shows your position, such as **1-10 of 104**.

The failure and blocker analysis cards each summarize the latest 25 matching runs in the scope.
They cover the selected time range independently of the table's page, search, and filters.

Rerun rows show **Original run** when you can open the retained source. If you cannot access that
source, the row says **Original run unavailable**.

Use [Run history and debugging](/automations/run/run-history-and-debugging) to interpret states,
diagnostics, and recovery actions.

## Related topics

* [Run history and debugging](/automations/run/run-history-and-debugging)
* [Trigger automations](/automations/trigger)
* [Set up automation integrations](/automations/connectors)


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