A scheduled export for one of our customers failed recently. It’s a weekly delivery that has been in place for nearly a year and has run without issue until recently. The error given was “Page load timeout after 60000ms”, and the Trace Id was

10c7cd9ac21a00d8

. Could someone look into this and explain why this happened?

The error message “Page load timeout after 60000ms” for a scheduled export indicates that the export process was unable to complete within the allotted time (60 seconds). This type of timeout is typically related to the time it takes to load and render the dashboard or its components before the export can be generated. Based on the knowledge sources, similar issues have occurred due to: - Large or complex dashboards: If the dashboard contains many insights, large datasets, or complex visualizations, it may take longer to render, leading to timeouts during export. - User permissions or data filters: If the user or service account used for the export does not have the correct permissions or is missing required data filters, the export may attempt to process the entire dataset, causing delays and timeouts. - Temporary platform or network issues: Sometimes, transient issues in the platform or network can cause timeouts, even if the export usually works as expected. Recommended steps: 1. Check dashboard complexity: Review if there have been any recent changes to the dashboard (e.g., added insights, filters, or data volume increases) that could impact load time. 2. Review user permissions and filters: Ensure the user or service account performing the export has the correct permissions and any necessary data filters applied, so it only processes the intended data subset. A missing filter can cause the export to process much more data than usual, leading to timeouts [see example](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1733961245102209?thread_ts=1733961245.102209&cid=C04S1MSLEAW). 3. Retry the export: Sometimes, the issue is transient. If the export works on retry, it may have been a temporary network or platform issue [see similar case](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1756895551232889?thread_ts=1756895551.232889&cid=C04S1MSLEAW). 4. Check for platform incidents: If the issue persists, check with GoodData support to see if there are any ongoing incidents or recent changes affecting exports. If you continue to experience this issue, providing the trace ID (as you have) to GoodData support will help them investigate further in their logs. Let me know if you need more specific troubleshooting steps or if you have additional details about the export or dashboard.

Well for those recommended steps: 1. The dashboard has not been edited since 30th September, so it is no more complex than the last time the scheduled export ran, but for some reason this execution timed out 2. The user has full access to the data which has always been the case 3. Our users rely on the export to avoid having to export directly from the GoodData UI. We would prefer that GoodData apply a retry mechanism on behalf of the users rather than pushing the obligation to them 4. As stated in my original post this is a weekly scheduled export. If the issue persists, it’s coming a full week since the last execution, so I would expect it to be related to export implementation details and not platform incidents Frankly it’s frustrating that the suggested fix to a broken scheduled export - that has been working perfectly fine up until now - is ‘do it yourself’.

Hi Eoghan, our apologies that the AI assistant wasn’t much help in this case - Our team are currently reviewing this and will get back to you ASAP with more details on what caused this issue.

Thanks @Michael Ullock!

Hi Eoghan, I am sorry to hear that it failed again - Can you please check for me if you try running the same export manually from the UI, does the report or dashboard export?

Yes manual export works.

Thanks for the confirmation - We will investigate this and get back to you with more details

Thank you Michael, we really appreciate it!

Hi Eoghan, I just wanted to let you know that I am going to go ahead and loop in our Tier 2 Technical team to have a look into this case for us. Someone from the team will reach back out with more details, as they become available.

Thanks for the update Michael

Hi Eoghan, my apologies for the troubles with scheduled export. The scheduled dashboard fails on a 60s timeout configured for a subcomponent handling scheduled export requests. We can see that the dashboard wasn’t able to fully load and be “ready” for sending it as a PDF attachement within the 60s timeout. The most time was spend on running generated SQL queries generated by the dashboard in the datasource. I have reached out to our engineering to review the possibility to extend the timeout for exports so it has a lesser probability hitting the timeout. I will let you know once I hear back from our developers.

Hello Jan - that’s great news, thank you for the update and the consideration. Fingers crossed it’s sufficient for our needs - many of our customers’ scheduled reports are running without issue, and hopefully this change addresses the few that hit this problem.