Issue Summary

After a Confluence Data Center to Cloud migration, link fixing leaves some Confluence page links unchanged, even though the target page is migrated and its ID mapping exists. The affected link uses the supported /spaces/<SPACE_KEY>/pages/<PAGE_ID>/<TITLE> format and has a long percent-encoded non-ASCII title. The link is not reported as updated, skipped or failed, so it does not appear in the audit log. Users cannot find these links from the report.

In one migration, 2,876 links in the same format and space were updated successfully. The unfixed link is 283 characters long. The longest link recorded in that site's audit log (186,963 rows over 9 runs) is 261 characters.

Steps to Reproduce

1. On Confluence Data Center with a context path (for example https://<dc-host>/confluence), create page A with a long non-ASCII title, so the page URL is longer than 270 characters.
2. On page B, add a link to page A in the /confluence/spaces/<SPACE_KEY>/pages/<PAGE_ID>/<TITLE> format.
3. Migrate both pages to Confluence Cloud with CCMA.
4. Run link fixing for Confluence on the destination site.
5. Open page B in Cloud and download the audit log.

Expected Results

The link on page B points to page A in Cloud. If it cannot be fixed, it is listed in the audit log as skipped or failed with a reason.

Actual Results

The link on page B still points to the Data Center URL. The audit log has no entry for it. The job shows as completed.

Workaround

Edit the affected links manually in Cloud. There is no report that lists them.