Every time an automation rule runs, Mateflow records it in the execution logs (automation history, run log). Use the logs to check that a rule did what you expected, find out why a run failed or was skipped, and run it again.
Who can do this: Owners and admins. Moderators don't see Automations. · Where: Web (admin console). · Plan: Automations depend on your platform plan.
Open the automation execution logs
Go to Admin → Automations → Execution Logs. The page lists runs from all your rules, newest first. Each row shows the Time, the Rule, the Trigger that started it, and its Status.
To see the runs of a single rule, open the rule from Admin → Automations → Rules. Its page has its own logs section.
Execution logs are kept for 30 days. Runs still in progress, or waiting on a delayed action, are never removed.
Filter automation execution logs
- Search logs: find runs by text, such as a rule name.
- Status: show one status, or All statuses.
- From and To: limit the list to a date range.
- Include test logs: runs you started with a test are hidden unless you turn this on. Test runs carry a Test label.
Click Clear to go back to the full list. Click Load more at the bottom to see older runs.
What each automation run status means
| Status | Meaning |
|---|---|
| Success | Every action ran. |
| Partial failure | Some actions ran and at least one failed. |
| Failed | The run failed. |
| Skipped | The rule didn't act, for example because its conditions weren't met. |
| Pending | The run is queued. |
| Running | The run is in progress. |
A run with delayed actions stays in progress until the last delayed action has run.
For a Skipped run, the row shows the reason, such as Conditions not met, Already ran once for this member, or Already ran once (global).
See the details of an automation run
Click a row to open Log details. It shows:
- Trigger data: the event that started the run.
- Action results: what each action did.
- Duration, and for a failed run the Error message, Error code, and Failure stage.
- Retries and Next retry, when Mateflow is retrying a failed action.
Common error codes include Timed out, Request rejected (4xx), Server error (5xx), Target not found, No target member, and Rule edited while waiting, Rule turned off while waiting, or Rule deleted while waiting for a delayed action whose rule changed.
Rerun an automation
To run the same execution again, open its Log details and click Rerun. You see Rerun queued, and the new run appears in the list, marked Rerun of an earlier execution.
Rerun isn't offered for test runs, or for runs that are still pending or running. Waiting for those to finish avoids running the same actions twice.
Fix the cause before you rerun a failed execution, for example the rule's settings or the webhook address it calls. See Automate tasks with rules.
Related articles
Was this guide helpful?