What are the jcr:frozenNode and nt:frozenNode in the CRX repository? And versioning error during replication in Workflow | Community
Skip to main content
avni27
avni27
Level 2
July 16, 2025
Solved

What are the jcr:frozenNode and nt:frozenNode in the CRX repository? And versioning error during replication in Workflow

  • July 16, 2025
  • 1 reply
  • 476 views

Hi Team,

I want to understand jcr:frozenNode or nt:frozenNode better in the CRX repository. I couldn't understand very well from the content available on the web.

Issue - There is a step in custom workflow to replicate one content is approved, Does the version information go along with the replicated page data to different environment? I think it should but it does not get updated in our use case which might be an issue.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by MayurSatav

Hi @avni27 ,

In AEM, jcr:frozenNode of type nt:frozenNode is used to store a snapshot of a node when a version is created. This node contains all properties and child nodes as they were at the time of versioning.

You can find these under /jcr:system/jcr:versionStorage in the CRX repository.


Regarding replication  when you replicate a page in AEM, only the current state of the node is sent to the publish environment, not its version history or jcr:versionStorage. This means the version information  including jcr:frozenNode does not get replicated by default. If you need version history on publish, you would need a custom solution.

1 reply

MayurSatav
Community Advisor and Adobe Champion
MayurSatavCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
July 17, 2025

Hi @avni27 ,

In AEM, jcr:frozenNode of type nt:frozenNode is used to store a snapshot of a node when a version is created. This node contains all properties and child nodes as they were at the time of versioning.

You can find these under /jcr:system/jcr:versionStorage in the CRX repository.


Regarding replication  when you replicate a page in AEM, only the current state of the node is sent to the publish environment, not its version history or jcr:versionStorage. This means the version information  including jcr:frozenNode does not get replicated by default. If you need version history on publish, you would need a custom solution.

avni27
avni27Author
Level 2
July 24, 2025

Thank you @mayursatav , We will work on creating something for version management between environments.

    Terms & ConditionsAccessibility statement

    Loading footer...