Test a rule and check its logs and history
Simulate a rule with sample data, review execution logs and see the version history of a rule.
BV
Written By Björn von KänelLast updated 14 days ago
Before you activate a rule, test it – no real actions are performed.
Who can do this: team members with permission to view automations (testing needs edit permission).
- In the rule list click … → Test run (or Test Rule at the bottom of the editor). Adjust the Sample Data (JSON) if needed and click Run Test. The result shows whether the Rule would trigger, how conditions were evaluated and which Actions Would execute.
- Click … → View logs to see executions of the last 30 days (or the last 100). Filter by status and date range.
- In the editor, click … (More actions) → History to see the version audit log of the rule.
Good to know
- Variables such as {{entity.name}} are shown as written in the test preview.
- A rule only writes logs when it is Active and its trigger fires.
- Currently the history can stay empty even after saving.
Related articles Automation rules overview · Create or edit an automation rule
Applies to VenueMaster3000 v0.53.1 (as of 2026-10-27)
Was this helpful?
Your feedback shapes what we write next.
Related articles
Automation rules overviewFind, filter and manage your if-this-then-that rules and start a new rule from a template.Create or edit an automation ruleDefine when a rule runs (trigger), optional conditions and what it does (actions), then save it as draft or active.Log maintenance and report defectsRecord repairs and checks for inventory items, follow them in the maintenance log and report broken equipment.Audit log – who changed whatReview every data change in your organization and set how long audit entries are kept.