Issue Summary

When exporting a single page to HTML from a very large Confluence Cloud space (around 100,000 pages), the export completes with an error in the UI, and the resulting ZIP file contains only index.html without the HTML file for the selected page.

Steps to Reproduce

1. In a Confluence Cloud site, prepare an extremely large space. In the customer’s case, the space has about 880,000 pages with content status = current.. Example from the customer: space key on https://<your_site>.atlassian.net/wiki.
2. In that large space, select a specific page as the only page to be exported.
3. Navigate to: Space settings → General → Export space → HTML.
4. Choose HTML as the export format.
5. In “Select the content to export”, choose Selected pages and select only the target page from step 2.
6. Start the export and wait for it to complete.
7. Download the generated ZIP file and inspect its contents.

Note: The space size is significantly larger than typical usage, but the export UI still allows selecting a single page and attempting HTML export, which then fails in a non-graceful way.

Expected Results

• The ZIP file should contain:
• index.html, and
• The HTML file for the selected page,
  so that the single selected page can be viewed offline as HTML.

Actual Results

This occurs in a space with over 800k current pages, where selecting a single page to export seems to generate a massive internal exclusion list (contentToBeExcluded for almost all other pages), causing the export to fail to generate the actual page HTML.

• The generated ZIP file contains only index.html and does not include the HTML file for the selected page.
• HAR captured during the export shows an extremely large number of contentToBeExcluded parameters being sent in the POST request to doexportspace.action, for example:
  Request:
  POST https://<your_site>.atlassian.net/wiki/spaces/doexportspace.action?key=<space_name>

contentToBeExcluded:ID_000001
contentToBeExcluded:ID_000002
contentToBeExcluded:ID_000003
contentToBeExcluded:ID_000004
contentToBeExcluded:ID_000005
contentToBeExcluded:ID_000006
contentToBeExcluded:ID_000007
contentToBeExcluded:ID_000008
contentToBeExcluded:ID_000009
contentToBeExcluded:ID_000010
contentToBeExcluded:ID_000011
contentToBeExcluded:ID_000012
contentToBeExcluded:ID_000013
contentToBeExcluded:ID_000014
contentToBeExcluded:ID_000015
contentToBeExcluded:ID_000016
contentToBeExcluded:ID_000017
contentToBeExcluded:ID_000018
contentToBeExcluded:ID_000019
contentToBeExcluded:ID_000020
...  

This suggests that when “Selected pages” is used in a very large space, almost all other pages are passed as an exclusion list (contentToBeExcluded), and the export process subsequently fails to generate the HTML for the selected page.

Workaround

• If the affected page is copied into a smaller space (with far fewer pages), exporting that copied page as HTML works as expected (ZIP contains both index.html and the page HTML).
• Therefore, as a temporary workaround, customers can:

1. Create a new / smaller space for export purposes,
2. Copy the target page (and optionally its parent) into that space, and
3. Run the HTML export for the copied page in the smaller space.

If no such smaller space is available or the page cannot be copied, the behavior cannot currently be avoided within the original very large space.