-
Bug
-
Resolution: Fixed
-
High
-
67
-
Severity 3 - Minor
-
8
-
Issue Summary
In Confluence, when a page has a lot of content (e.g. macros, information from macros, attachments and a lot of images), the page will take some time to render, but, indeed, either it will not be rendered, or, a timeout like the following will be displayed:
Error: GraphQL error: Timeout error querying the remote graphql service.
Steps to Reproduce
- In Confluence, make sure to create a page that will have a lot of content to be rendered. Specific examples could be related to the User list macro when trying to retrieve the users from a (default, mostly) group with a lot of users (like 2000).
- If there are no errors saving the content, try to publish the page.
Expected Results
The page should render properly, or, after a while, have the content rendering properly.
Actual Results
The page will take a while to load, and eventually, it will fail with a message like above, or, simply not have the content rendering, with only errors from the browser's console.
Notes
Reports and tests come typically from the following scenarios:
- Pages using multiple Jira issues macro separately, or, using a JQL that will retrieve a lot of content.
- Using the user-list macro with default groups like confluence-users when having a lot of users.
- Blog Posts macro when using the parameter to show all the content of the blog and having a lot of blogs on the instance
- Multiple "Excerpt-includes" macros on the page.
- Multiple "Expand" macros on the page
- Content by label macros with a lot of pages to be rendered
Workaround
Split the content of the pages into multiple pages, or, use a simple view method from macros that allow so, like the "Blog Posts" macro.