Every time an automation rule runs, Mateflow records it in the execution logs (automation history, run log). Use tests and logs to check that a rule does what you expect, 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.
Test an automation rule before turning it on
New rules are saved turned off, so you can test them first. Click Test rule on the rule's page, or on the form before you save. A test is a dry run: it checks the trigger and conditions and fills in the text, but never runs actions.
- Under Trigger data, choose Sample data or the Latest real event in your community.
- Optionally pick a Member (optional). Member conditions, such as points, tags, and days since joining, are checked against that person. With sample data and no member, they don't pass.
- Click Test rule.
The result is drawn on the rule: each condition shows Passed or Not met, and actions that wouldn't run show Won't run. Tests ignore How often, so a test can pass for a member the rule already ran for. When a real event wouldn't run the rule for that reason, a note at the top of the result says so and says when the rule ran.
Run an automation rule now
Run now on a rule's page runs the rule for real. Pick a Member to run it as if they triggered it, or leave it empty and use sample data. It sends real notifications, points, tags, space changes, and webhooks.
Without a selected member, review the supplied trigger-data JSON before running. It must be an object, such as {}; arrays, null, and scalar values are rejected. A queued run opens its log when available. Event lifecycle triggers cannot use Run now.
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 Member, the Trigger that started it, and its Status. To see one rule's runs, open the rule from Admin → Automations → Rules.
At the top, Overview shows runs, success rate, and duration for the Last 24h, Last 7 days, or Last 30 days, with a Run trend, Failures, and Errors by type. Click a rule under Most active rules or Rules with most errors to open it.
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 by rule name or trigger.
- All rules: pick one rule.
- All members: pick a member, for example to see why someone didn't get a welcome notification.
- Status, and a date range.
- Include test logs: test runs are hidden unless you turn this on. They 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 here until the last one has run. |
For a Skipped run, Log details shows the Skipped reason, such as Conditions not met or Your plan doesn't include automations, so rules are paused. On a phone's browser, the row shows it too.
Why an event isn't in the automation logs
Mateflow doesn't log every event a rule ignores, so a member can be missing from the logs even though the rule is on. These leave no entry:
- The event doesn't match the rule's trigger settings, such as its space, event, or points threshold.
- The event fails a Trigger space or Content type condition.
- The rule is set to Once per member or Only once and has already used that run. Look for the earlier Success run, or test the rule with that member.
Conditions about the member, such as tags, points, and days since joining, do log a Skipped run.
See the details of an automation run
Click a row to open Log details. It shows:
- The Member and what the run was about, such as a post, event, or course.
- Only if (Conditions): each condition with Passed or Not met and the actual value. After one fails, the rest show Not checked (an earlier condition already failed).
- Trigger data and Action results, including Sent to a number of members and when a delayed action is Due.
- Duration, and for a failed run the Error message, the Failure stage, and an error code on each failed action.
Common error codes include Timed out, Request rejected (4xx), Server error (5xx), Target not found, No target member, Points are turned off for this community, The course is full, and Rule edited while waiting for a delayed action whose rule changed.
Rerun a failed automation
Failed actions aren't retried automatically, so you can rerun Failed and Partial failure runs from Log details. Test runs can't be rerun.
- Rerun failed actions: only the actions that failed run again, right away and without their delay.
- Rerun whole rule: every action runs again with the original trigger data. Notifications and webhooks are sent again, but points already awarded aren't awarded twice.
Confirm in Rerun this execution?. You see Rerun queued, and the new run is marked Rerun of an earlier execution. Fix the cause first, such as the rule's settings or the webhook address. If a rule fails 5 times in a row, the owner and admins are notified, and the rule stays on until you turn it off. See Automate tasks with rules.
If the saved rule changed, or an older log lacks the action history needed to identify failed actions safely, partial rerun may be rejected. Review the current rule before choosing a whole-rule rerun, which can send messages again. Date filters use UTC day boundaries, and duration includes waiting for delayed actions; duration and error breakdowns may use capped samples.
Catch up on a skipped automation run
A run skipped because of your plan or its conditions can be run after all, for example after you upgrade or add the tag the member was missing. Click the run to open Log details, click Catch up, and confirm in Catch up on this run?. Test runs can't be caught up.
The event runs now with its original trigger data: the conditions are checked again, and if they pass, the actions run. How often still applies, so if the rule has already used that run, you see an error and nothing is sent.
For event lifecycle runs, catch-up rechecks the current schedule, rule, access, audience, and notification preferences. It cannot force an expired notification to send or bypass a personal reminder that owns the time slot.
Related articles
Was this guide helpful?