Page version history Page IDs are randomised

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform Notice: Server and Data Center Only. This article only applies to Atlassian products on the server and data center platforms.

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
Main page ID 500101
\----  Current 500101
 \----  v.3		500105
  \----  v.2	 500104
   \----  v.1	  500102

However, 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
Main page ID 500101
\----  Current 500101
 \----  v.3		500105
  \----  v.2	 500202
   \----  v.1	  500104


Diagnosis

Check if the Space where page with scrambled page version IDs has been imported, than than created in that instace

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 result in new Content IDs being generated for each piece of content being imported, however, any new page versions created after import will continue to follow increasing numeric content ID pattern.

Last modified on Nov 30, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.