Accessing Space Settings Trash throws error

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: High
    • Component/s: Page - Delete
    • None
    • 13
    • Severity 3 - Minor
    • 10

      Issue Summary

      If the space page trash has a large amount of content. Users will be unable to load the space trash UI for that space.

      We have seen this behavior with spaces that have ~700,000 pieces of content in the space trash.

      Steps to Reproduce

      1. Navigate to space
      2. Navigate to space settings
      3. Navgiate to trash

      Expected Results

      Space Trash UI should load.

      Actual Results

      The UI and browser network tool throw the below errors:

      UI Error

      Something went wrong.
      We're moving mountains to get it sorted.
      View our status page and subscribe for
      service updates.
      

      Browser Console Error

      Request URL: https://<instance-url>.atlassian.net/wiki/pages/viewtrash.action?key=<space-key>
      Request Method: GET
      Status Code: 504 Gateway Timeout
      

      Workaround

      We recommend using the API to delete items and review the list of trashed pages, for example, using the below endpoint and some pagination:

      https://<instance-url>.atlassian.net/wiki/api/v2/spaces/<space-id>/pages?status=trashed
      
      https://<instance-url>.atlassian.net/wiki/api/v2/spaces/<space-id>/pages?status=trashed&limit=250&start=1

      And then restore the page using the API or the common restore URL, for example:

      https://<instance-url>t.atlassian.net/wiki/pages/restoretrashitem.action?key=<space-key>&contentId=<content-id>
      

      Alternatively, the pages can be purged using following delete API -

      DELETE https://<instance-url>.atlassian.net/wiki/api/v2/pages/<page-id>?purge=true
      

            Assignee:
            Andrew W.
            Reporter:
            Isaac Spann
            Votes:
            4 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: