要約

The automation rule fails with the error message "Actor does not have permission to view the event that triggered this execution." and you can't identify the root cause.

診断

Automation uses a rule processing queue to manage the execution of rules in your instance. To maintain performance, rule executions are queued, and the number of items processed in parallel is limited. When the instance has several automation rules using the same trigger (e.g., Issue Created), those rules often won't be executed in parallel due to this processing queue, which can delay access to an issue by the automation rule actor.

原因

The error message "Actor does not have permission to view the event that triggered this execution" is most often related to an issue ticket that was deleted by a different automation rule or manually deleted while the executed automation rule was in a queue to be processed.

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

You can see an example in the screenshot below:

ソリューション

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

• Transition the issue ticket to a Closed/Canceled status rather than using the Delete Issue action.
• 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 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 Rule Details.
• See the Best practices for optimizing automation rules to improve your automation rules.

参考

• キューのアイテム数のサービス制限
• Check the audit log
• 自動化ルールの最適化に関するベスト プラクティス