How to Read the Automation Activity Log in CrmLeaf
All editions. Requires the Workflow Automation add-on and the permission to view automations.
Availability: All editions. Requires the Workflow Automation add-on and the permission to view automations.
Overview
Every time a rule is evaluated, one row is recorded on the Activity tab, including the times it did not match. This is how you answer "why did or did not a rule fire?".
How It Works
The strip at the top counts what is running now and the runs, matches and failures of the last hour. Each row shows when it happened and the trigger, the rule, the record (a link, where the record still exists), the outcome, a reason where there is one, how long it took, and a badge per action in the order they ran. Hover the info icon beside a reason for the full text. You can filter by date range, rule or outcome, or search.
Outcomes
| Outcome | Meaning |
|---|---|
| Matched | The conditions passed and the actions ran |
| Did not match | The rule was looked at; the record did not qualify |
| Failed | The rule itself could not be evaluated |
| Skipped | The rule deliberately did not run (automations paused, or a bulk change) |
| Running | Still in progress |
An action badge is Done, Failed, Not run (skipped after an earlier failure or the time limit) or Still running.
"Matched" can still contain a failure. If the conditions passed but an action failed, for example nobody to notify or a webhook that returned an error, the run is Matched, the failed action's badge is red and the Why column says what went wrong. The "Failed in the last hour" counter counts these too.
How long history is kept
History is kept for 30 days by default and cleared automatically every night. An administrator can change this under Workflow Automation Settings → Execution history; leave it empty for the default.
Prerequisites
- The permission to view automations.
- At least one rule that has been evaluated since it was made.
For Administrators
Step 1: Find the run
What to do: Open the Activity tab and filter by rule, outcome or date range.
What to verify: A row exists for the record you are asking about. If there is no row at all, the trigger never evaluated: the trigger was wrong, or an "updated" rule's field did not change.
Step 2: Read the outcome and reason
What to do: Read the outcome and open the Why column. Check each action badge.
What to verify: You can tell whether the record did not qualify, an action failed, or the run was skipped. The reasons are explained in Limits, Safety Nets and Troubleshooting.
Expected Result
You can say, for any record, whether a rule looked at it, what it decided, and what each action did.
Important Notes
- Menu names and their position can differ between product editions and can be customised for your account, so your sidebar may not match these paths exactly. Use Search or your Quick Access items if you cannot find a screen.
- Failures never interrupt the person saving the record; they are recorded here instead.
- Deleting a rule hides its history from Activity.
- Activity shows only runs of rules you can see, so two people can see different lists.
Troubleshooting
| Issue | Possible Cause | Resolution |
|---|---|---|
| No row for a record you expected | The trigger did not evaluate: wrong trigger, a field condition that did not change, or the record was saved before the rule existed | Check the trigger and conditions, then save the record again after the rule is active. |
| A run is Matched but nothing arrived | An action failed inside a matched run | Look for a red action badge and read the Why column. |
| Old runs are missing | History is cleared after 30 days by default | An administrator can change the period in the settings. |
| The Activity tab shows fewer runs than a colleague sees | It shows only runs of rules you are allowed to see | See Who Can See and Change Automations. |
Frequently Asked Questions
Why is there a Did not match row?
The rule was evaluated and the record did not qualify. It is recorded so you can see the rule ran.
Does a failed action stop the run from showing as Matched?
No. The run is still Matched; the failed action's badge is red.
Related Articles
Our support team answers on business days. Reference WFA-06 so we can jump straight in.