Why an automation didn't run

The step-by-step diagnosis when a rule "just didn't fire."

Automations are a pipeline: trigger → conditions → actions. Find out which stage didn't happen.

Follow these steps:

1. Open Automation > Logs and look for the expected run.

2. If there's no log entry, the rule isn't active (pause it and resume), or the trigger never fired in the expected form — check the trigger's event type matches what actually happened.

3. If there's a log entry but no action, a condition blocked it. Review condition values against the actual record — all conditions must match.

4. If the action failed, read the error message in the log: typically bad recipient, missing permission, or a disconnected integration.

5. Confirm scope — if the rule is department-limited, the event must belong to that department.

6. Test again after fixing — run the trigger and re-check the Logs.