Automations: check runs and errors
Under Settings → Automations → Executions you can see what a rule triggered during an event. This view helps with both missing actions and unexpected messages or templates.
Find the appropriate execution
- Limit the list by rule, event, and status, or use the search.
- Compare the time and object reference with the affected booking, person, or offer.
- Open the execution detail. There you will find the rule, event, start time, and duration.
- First read the Conditions and then the Actions.
If an execution is completely missing, check plugin authorization, active rule, trigger, and the time of creation. A subsequently activated rule does not automatically process all previously created data records.
Read results correctly
| Display | What you check |
|---|---|
| Pending / in progress | The action is not yet complete. Update later and check the individual actions. |
| Successful | The logged actions have been processed. Additionally, check the outbox for email delivery. |
| Skipped / not met | Review the conditions, priority, and the specific notice; a deliberate non-execution is not automatically an error. |
| Failed | Read the error message of the affected action and correct its prerequisites. |
A run can contain multiple actions. Therefore, evaluate each action individually; a successful tag change, for example, does not prove that an email was also sent.
Review templates and notes
Template actions display the stored details of the template used. If available, you can open the current template. This preview shows its content today; subsequent changes to a template do not retroactively alter the already sent document.
For a note action, the subject and target contexts are visible. Open the person or booking and check the note there. The masked input data supports diagnosis; it is not a complete export of all personal data values.
Fix the cause and check the result
- Pause a rule if it repeatedly triggers unwanted new actions.
- Check for missing or deleted templates, invalid field/tag assignments, recipients, and contradictory conditions.
- For displaced template actions, check other rules for the same event and their priority.
- Save the correction and simulate it with a suitable object and a counterexample.
- Reactivate the rule and check a new controlled event and its result.
An already sent message or data change is not undone by pausing. Repeat a business process only after you have checked its previous outcome to avoid duplicate messages.
Example: Certificate uses the wrong template
The course instructor opens the certificate dispatch execution. The conditions of the intended rule are met, but its PDF action was superseded by a higher-priority rule. The team narrows the scope of the general rule, simulates both offer cases, and checks the selected template and generated PDF the next time a certificate is sent.
Next: Create rules · Outbox · Email templates
Distinguish between rule test and logged run
A rule test evaluates the saved draft on the selected example object. A run belongs to an actual event and may already contain processed or pending actions. Later changes to the draft do not retroactively correct an earlier run.
If a PDF replacement was skipped, check the event, template type, compatibility, and higher-priority rules. Then open the actually generated participant document. A green result from another action does not confirm the correct PDF selection. See Select templates before dispatch.