Improve audit log error for content restricted to rule actor

XMLWordPrintable

    • 6
    • 21

      Automation rules that run on restricted content leave a vague error in the audit log. Below is an example:

      Page published
Failed to fetch page info
Trace ID: 95014a58-7cae-40d0-825b-8efda74e8155::00::95014a58-7cae-40d0-825b-8efda74e8155
      Failed to add the labels:
to-be-archived-tech. Trace ID: 2133f7e3-2132-4df5-b931-c1e4484bbc68::01::2b08e5a3-935c-4f5c-9c74-6b177753c745, 

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

      Many users would benefit from more detailed error messaging. This can hopefully help end-users troubleshoot the errors that automation rules throw when engaging in restricted content.

       

       

      Feb 2025 - Notes

      Improvements were made and the error message for lack of permissions was changed to:

      Failed to fetch page info. It may not exist, or you may not have permission to view it.
Trace ID: xxxxxxxxxx-b9a3-4dde-b600-xxxxxxxxxx::00::xxxxxxx-b9a3-4dde-b600-xxxxxxxxxx

            Assignee:
            Unassigned
            Reporter:
            Isaac Spann
            Votes:
            21 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: