Summary

All HTTP requests in Cloud have a 60 second timeout. When a Word export runs longer than that, the task keeps running on the background but the generated export file does not returned to the customer. Confluence throws the "Page Unavailable" error to customer.

If another Word export is triggered, Confluence tries to generate it again. Because there is a 30 second retry done automatically by the smart-status timeout page from the client browser that will trigger a new word export automatically.
This loop of generating new word exports can render Cloud sites unusable on certain situations.

Environment

• Confluence Cloud

Steps to Reproduce

1. Create a Confluence Cloud page with more than 350 JIRA Issue macro
2. Export page to Word

Expected Results

Word file is downloadable at the end of the process.

Actual Results

"Page Unavailable" page is showing.

Workaround

No workaround