Investigate rule activity and skipped actions
Use recorded execution details to understand the result instead of guessing from the rule name.
- Permission to inspect automation activity.
Step-by-step walkthrough
- 01
Open the relevant automation rule and choose Activity. Find the run associated with the event you are investigating.
- 02
Inspect the event, rule version, condition result, and action outcomes. A skipped action may reflect eligibility or changed state rather than an outage.
- 03
Compare the recorded result with the current ticket and its ownership. Remember that the rule definition may have changed since that run.
- 04
Correct the draft only after identifying the cause. Test and publish a revised definition, then verify a new controlled event.
A closer look at the interface
These are actual product captures from a fictional demo workspace. Navigation and available controls can differ by role, configuration, or release.
Automation version history
- 1Choose the published version to inspect.
- 2Compare event, conditions, and actions.
- 3Restore to draft; review and publish separately.
Expected result
An explanation tied to the recorded run and its rule version.
Important details
Changing a rule does not retroactively change earlier execution records. Do not repeatedly trigger customer-facing actions just to investigate a run.
Need help with this workflow? Contact the team and include this guide’s title.