{
  "id": 11766215,
  "title": "Repair the Confluence Cloud pages your migration quietly broke, one space at a time",
  "url": "https://urgent.news/2026/10/03/repair-the-confluence-cloud-pages-your-migration-quietly-broke-one",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-03T20:45:25.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/mihai_leanzero/repair-the-confluence-cloud-pages-your-migration-quietly-broke-one-space-at-a-time-27jg"
  },
  "original_language": "en",
  "account": "To fix broken Confluence Cloud pages after a migration, follow these steps one at a time. Begin by granting yourself space admin rights, as site admin does not include this permission. Use the Node.js script grant-space-admin to add your API token user as an administrator on each space. Verify the dry run output before applying changes.\n\nNext, before trusting any discovery queries, dump the raw storage XML of a few matching pages from your tenant. Storage format varies by app version, so this step ensures you are working with the correct format. Run the sync_html_macros.js script with the --space and --limit options to produce a reviewable plan file.\n\nRead the generated plan file carefully. It lists affected pages and allows you to verify what needs to be repaired. Once you are confident in the plan, execute the fix by running the script without the --plan-only flag. The tool will process each page, repairing broken HTML macros and resolving identity parameters that still hold DC usernames.\n\nAfter the migration, check the rendered page to verify the fix. This is the only check that can honestly fail, ensuring the pages work as intended. By following these steps one space at a time, you can safely repair Confluence Cloud pages without disrupting your entire site.",
  "summary": "Repair the Confluence Cloud pages your migration quietly broke, one space at a time Key takeaways END STATE: one space repaired, with a reviewed JSON plan, a backup of every original page, and the fix confirmed in a browser rather than in a 200 response. Site admin is NOT space admin. Grant yourself space admin first or the run collects 403s for an hour. A storage-format rewrite that is…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 2,
    "also_reported_by": [
      {
        "outlet": "Dev.to",
        "title": "Jira Data Center heap size and JVM tuning for a Cloud migration: setenv.sh and JCMA",
        "url": "https://urgent.news/2026/10/03/jira-data-center-heap-size-and-jvm-tuning-for-a-cloud-migration",
        "published": "2026-10-03T17:34:39.000Z"
      }
    ]
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}