Summary

When a user tries to load a page which contains the Attachment macro with tons of attachment files, the page may show one of the errors below:

Something's gone wrong.
Our team has been notified. If the problem persists, please contact Atlassian Support.

Error: Rendering this content exceeded the timeout of 30 seconds

Steps to Reproduce

1. Create a "File list" page (or add "Attachment macro" to an existing page)
   • 
2. Upload a lot of files to the page
   • I could reproduce the timeout error with 1200 text files (you can generate dummy files by snippet.sh)
   • 
   • The upload tends to take time and fail due to "JwtAuthoriser: TokenExpiredError". If you face the error, reload the page and keep uploading the remaining files.
   • 
3. Load the page and confirm the errors
   • 
   • 

Expected Results

The page with the Attachment macro successfully lists up the attachment files.

This should be paginated to deal with large number of attachments.

Actual Results

When the error "Something's gone wrong" occurs, the browser console complains the timeout error as below:

GraphQL error: Timeout error querying the remote graphql service

The requests to the URLs below take more than 50s to respond:

• /wiki/rest/graph
• /cgraphql

Workaround

Currently, the only available workaround is to split the attachments into multiple pages, keeping 500 attachments or less on each page.