Skip to main content
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

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