Actor permission error in automation execution log

Summary

The automation rule fails with the error message "Actor does not have permission to view the event that triggered this execution."

Diagnosis

Automation manages rule execution with a processing queue, limiting parallel processing to maintain performance. If multiple rules share a trigger (e.g., Issue Created), they may not run simultaneously, delaying issue access for the automation rule actor.

Cause

Most common cause: the triggering issue was deleted (by another rule or a person) while this rule was queued, so the actor can no longer “view the event”. It is usually a race condition, not a real permission gap.

On the Global Automation> Audit Logs page, you can identify/count how many rules are executed for the same issue ticket; this will also help you find the automation rule that deleted the issue (if any) using this action.

Solution

As possible solutions to avoid this error, you may consider one of the following:

• Replace Delete Issue actions with a transition to Closed/Canceled where possible.

• Review the trigger for all automation rules executed for a single issue, and consider using Field value change as a trigger/action to cascade the execution rule if it is dependent. 

  • You can use the "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule" in the Rule Details.

• Use the Audit Log to count how many rules fire on the same trigger (e.g. Issue Created) and consolidate them.

• Add an issue-exists condition early in the rule.

• See the Best practices for optimizing automation rules to improve your automation rules.

References

• Queued items service limit

• Check the audit log

• Best practices for optimizing automation rules

• Resolve 'Actor Permission' automation error