Confluence global automation error: “The flow actor doesn't have permission to view the event that t

[Muhil Varnan]

We have a global Confluence automation triggered on Page published which sends a webhook. Intermittently the rule fails with:

```

The flow actor doesn't have permission to view the event that triggered this flow

```

The actor user has the right permissions to view the spaces/pages covered by the rule scope.

However, the automation audit/error log doesn’t include page details (no pageId, space, or content link), so it’s hard to debug which page/event caused the failure.

What I need help with

1. In Confluence automation, what are the common root causes for this error even when the actor can view the space?

2. How can we reliably identify the exact page that triggered the failed execution?

   • Is there a way to show pageId / page URL in the audit log?

   • Can we add {{page.id}} or similar variables to logs, and where do they appear when the rule fails early?

   • Any recommended workaround to capture the page context (e.g., logging, sending to webhook, smart values, etc.)?

Context

• Trigger: Page published

• Rule type: Global automation, scoped to multiple spaces

• Action: send webhook (Confluence → external sync)

Any guidance or best practices to debug this would be appreciated.

[Gina Paciulli - XALT]

Hi @Muhil Varnan

I am getting the same error but in Jira. 

This error only occurs on runs where the audit log Scope column shows "Global."

The same rule succeeds consistently when the audit log attributes a run to a specific project or to "Multiple spaces."

I've ruled out a genuine permissions gap on our end since the rule runs successfully against individual projects and the owner of the rule is an Org Admin and has full access across all projects.

[Bill Sheboy]

Hi @Muhil Varnan 

For automation questions, it helps to provide context with images of the complete rule and audit log details showing the execution.

Until we see those...

With which step in the rule are you seeing that error: the trigger, the Send Web Request action, etc.?

With the Page Published trigger, the {{page.id}} smart value should be available.  However, there could be racetrack timing problems when using that value in different rule actions.  I recommend perhaps building the entire URL and first storing that with Create Variable...and then using that variable in the Send Web Request action.  This will ensure the the smart values fully evaluate to build the URL before it is needed.  Same thing if you are sending a message with the endpoint which contains smart values.

Kind regards,
Bill