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

# Review automation executions

> Explain successful, skipped, partial, and failed automation runs.

An execution records how an automation evaluated a reading and what happened to each action. Use it as the primary audit trail when a workflow produces an unexpected result.

## Execution outcomes

| Outcome | Meaning                                                           |
| ------- | ----------------------------------------------------------------- |
| Success | Every eligible action completed                                   |
| Partial | At least one action completed and another failed or was skipped   |
| Failure | The run could not complete its required actions                   |
| Skipped | Conditions prevented the run or every action remained in cooldown |
| Running | The workflow is still processing                                  |

## Review an execution

1. Open **Automations** and select the automation.
2. Open **History**.
3. Select an execution.
4. Review the source reading and trigger evaluation.
5. Review each optional condition and its reason.
6. Review actions in order, including cooldown and error details.

## Troubleshoot a missing or skipped action

Check these items in order:

1. The automation is active.
2. The expected reading reached the correct meter.
3. At least one OR clause matched the reading pattern.
4. Every required condition passed.
5. The action's cooldown had elapsed.
6. Referenced assets, templates, users, teams, parts, and email recipients remain valid.

Correct the rule or dependency, then submit a new reading when another evaluation is appropriate. Existing executions remain unchanged.

## Deletion boundary

Deleting the automation removes it and its History tab from normal product views and prevents new runs. Canary retains the definition and execution records for audit and recovery. Records created by prior actions, including work orders, also remain available in their own histories.

## Related pages

* [About automations](/help/automations/overview)
* [Create an automation](/help/automations/create-automation)
* [Record meter readings](/help/meters/readings)