Issue Summary

Let say customer performs a C2C migration for multiple spaces and then if customer founds an issue with one space and that space is deleted-exported from source, and imported on the destination.

Now Link Fixing is triggered from UI it will update the all the links correctly but the space which was imported via export import is updated with correct domain but page ids that were generated during Transfer Data migration.

Expected Results

Link fixing to work correctly and mapping should be updated with new page ids generated after importing the same space, or should give info/warning/hint about link fix may incorrectly update if there is an import of the same space after deletion.

Actual Results

domain correctly updated, but pageids incorrectly updated

Here is an example of a Jira issue (under remotelinks) in which the Confluence links were updated incorrectly:
https://destination.atlassian.net/browse/ABC-1.

The original link was:
https://source.atlassian.net/wiki/spaces/xyz/pages/3881205851/pagetitle

After the link-fixing process, it was changed to:
https://destination.atlassian.net/wiki/spaces/xyz/pages/42189601/pagetitle
NOTE: 42189601 is the page id that was mapped when the first C2C migration was completed

However, the correct link to the referenced page after migration should be:
https://destination.atlassian.net/wiki/spaces/xyz/pages/44458851/pagetitle
NOTE: 44458851 is the page ID that was generated after space was imported manually after the deletion of the space transferred by the C2C migration

Workaround

Legacy link fixing to be used for impacted space followed by link fixing via UI OR only legacy link fixing