Page version history Page IDs are randomised
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When looking at Page History, sometimes page IDs for previous page versions would appear in random or non increasing order. As page IDs (content ID) are not recycled, every new page version should have a higher numeric ID than previous version.
Example Expected
1
2
3
4
5
Main page ID 500101
\---- Current 500101
\---- v.3 500105
\---- v.2 500104
\---- v.1 500102However, in some situations, page version ins page history will have page IDs in randomised order, with some pages being significantly higher or lower than others in the list.
Example Unexpected
1
2
3
4
5
Main page ID 500101
\---- Current 500101
\---- v.3 500105
\---- v.2 500202
\---- v.1 500104Diagnosis
Check if the Space where page with scrambled page version IDs has been imported, rather than created in that instance.
Cause
When importing space into Confluence, content being imported will receive new content IDs in the order of import, rather than logical content structure.
If a certain page version has a lot of content in it, it will take longer to import than page version with less content on it. As import threads are running in parallel, this might result in older page versions getting imported faster than newer, bigger ones, which would result in older page versions having higher numeric page IDs values as they got allocated one faster.
Solution
There is no workaround, as Space import will always generate new Content IDs for each piece of content being imported. However, any new page versions created after import will continue to follow an increasing numeric content ID pattern.
Was this helpful?