Issue Summary

The User Access Audit tool (/wiki/admin/user-access) throws an intermittent "Something went wrong on our end" error (Hash: g32fbl) when checking Read-Write (Edit) access for a user on a page that has inherited edit restrictions from a parent page. The tool should gracefully report that the user does not have edit access — rather than throwing an unhandled error. 

It is intermittent at time and even randomly on the user audit page while selecting a user as well.

Steps to Reproduce

1. Navigate to /wiki/admin/user-access on a Confluence Cloud site (sandbox or production)

1. Enter a user account ID or type user name

1. Select Read-Only access check → ✅ Works correctly, returns results

1. Select Read-Write access check on a space where:

• • The space has no edit restrictions

• • The root/ancestor page has an edit restriction set (inherited by all child pages)

• • The checked user is NOT in the allowed editors list

1. Result: Intermittent "Something went wrong on our end" error with Hash g32fbl

Expected Results

The User Access Audit tool should gracefully return a result indicating the user does not have Read-Write access due to page-level content restrictions — similar to how it handles Read-Only checks. No error should be thrown.

Actual Results

The tool throws:

Something went wrong on our end Hash: g32fbl

This occurs intermittently — sometimes the GraphQL query (UserAccessPageUserPermissionsQuery) succeeds and correctly returns hasRestriction: true / hasInheritedRestriction: true. Other times, it fails with the generic error.

Root Cause Hypothesis

The Read-Write permission check performs a more complex query path than Read-Only:

• It must evaluate EDITSPACE + CREATEEDIT permissions

• It must traverse the page restriction inheritance tree to resolve inherited restrictions

• When the restriction owner is a deactivated user, the permission graph traversal may encounter an edge case (orphaned permission record) causing intermittent failures

• The bulk enumeration across all spaces amplifies the likelihood of hitting this timeout/exception

Workaround

Check permissions directly via Space Settings → Permissions or inspect the page-level restrictions via the padlock icon on the ancestor page.