Issue Summary

Exporting a space into HTML for a space with a deep page hierarchy may result in errors or an empty file

Steps to Reproduce

1. Create a Confluence Cloud space with a deep and complex hierarchy
2. Assume 10.000 top level pages
3. For some of the top level pages, create descendant pages/content around 7 levels deep
4. Ensure there are top level pages with several hundred descendant pages (not a single page extending 7 levels deep)

Consider simulating a whole Confluence site as a single space:

• Project Alpha home
  • Alpha green
  • Alpha blue
    • Alpha blue dolphin
      • Alpha blue dolphin eating
      • Alpha blue dolphin grazing
        • Alpha blue dolphin grazing aggressively
          • Alpha blue dolphin grazing aggressively to the left
          • Alpha blue dolphin grazing aggressively to the right
          • Alpha blue dolphin grazing aggressively upside down
            • Alpha blue dolphin grazing aggressively upside down in water
            • Alpha blue dolphin grazing aggressively upside down in mud
        • Alpha blue dolphin grazing nonchalantly
        • Alpha blue dolphin grazing wildly
    • Alpha blue llama
  • Alpha red
• Project Beta home
  ....
• Project Epsilon Phi Omega home

1. As a space administrator, export the space.
2. Select HTML
3. Export only children of Project Alpha home

noting a full space export succeeds.

Expected Results

Partial space can be exported successfully

Actual Results

Space exports with an empty 0KB file.

Workaround

Export the full space.
Remove undesired contents.

Due to the large size of the content tree, not all selected checkboxes are being captured in the backend array contentToBeExported. Consequently, the backend receives a blank list of contentToBeExported arrays.