Issue Summary

During a Cloud migration using CCMA (Confluence Cloud Migration Assistant) with the Comala Document Management app, the GET /spaces endpoint returns no spaces when queried programmatically — but returns a 200 OK with the expected data when the same spaces have been manually visited in the browser beforehand.

Steps to Reproduce

1. Set up a Confluence Cloud instance with spaces that have been migrated but not yet manually visited in the UI
2. Perform a migration using CCMA with Comala Document Management
3. During migration, call GET https://your-instance.atlassian.net/wiki/api/v2/spaces programmatically to identify created spaces
4. Observe: the response is 200 OK but returns an empty or incomplete spaces list

Expected Results

GET /spaces returns all created spaces regardless of whether they have been visited in the browser.

Actual Results

GET /spaces returns no spaces. Re-running the migration after manually visiting each space in the browser resolves the issue, suggesting the spaces are not fully initialised until first accessed via the UI.

Workaround

Manually visit each migrated space in the Confluence Cloud UI, then re-run the migration.

Additional Notes

• The endpoint returns 200 OK in both the broken and working states — there is no error signal to the caller
• Reproduced via Postman independently of the CCMA tooling
• Strongly suggests a lazy initialisation issue: spaces created by migration may not be fully indexed/available to the API until a UI access triggers some post-creation setup step
• Affects cloud Migrations