DocumentationExperience Cloud KCS

Content Fragment content reverts and unexpected versions are created in Adobe Experience Manager

Last update: October 21, 2026

This article explains why Content Fragment content in Adobe Experience Manager (AEM) may revert to an older version and why new versions are created when opening and closing a fragment, even without making changes. It provides steps to investigate and resolve these behaviors.

Description description

Environment

Adobe Experience Manager (AEM), all supported versions

Symptoms

  • Content Fragment content appears to revert to an older version after updates.
  • Opening and closing a Content Fragment in the editor without making changes creates a new version each time.
  • No evidence of standby author server, synchronization, or caching issues is found in logs.

Cause

These symptoms are consistent with standard AEM versioning and publishing behavior:

  • Edits made on the author instance are not visible on publish until the fragment is republished.
  • Opening a Content Fragment in the editor can trigger versioning events, even if no changes are made, due to how edit sessions are managed.
  • No evidence of standby server, synchronization, or caching issues was found.

Resolution resolution

Follow the steps below to investigate Content Fragment version and publishing behavior:

  1. Review the Content Fragment’s properties. Compare cq:lastReplicated (last published) with jcr:lastModified (last modified on Author). If the fragment was edited after its last publication, Publish continues to show the last published content until you republish the intended Author version.
  2. Verify the Author environment configuration and confirm that only one Author instance is processing requests for the affected Content Fragment path. Review the logs to verify that no standby or secondary Author instance is involved
  3. Open the Content Fragment’s Version History and compare the current version with earlier versions. Note the version labels and timestamps. AEM creates a safety version when an edit session starts; closing without saving restores the session’s starting version. Do not treat a status change alone as proof of content loss.
  4. If Publish still shows stale content after you verify the Author version and republish it, review the applicable Dispatcher and AEM logs for caching errors or stale responses. The absence of a cache error in the logs does not, by itself, rule out caching.
  5. If new versions appear without intentional edits, identify which Content Fragment editor was used and review relevant editor customizations, overlays, or workflows. Reproduce the behavior in a controlled environment before changing configuration.
  6. If the editor uses autoSaveInterval, check the configured value. The documented default is 600 seconds; the value can be overridden under /conf. Do not change the default solely to address unexpected versions without confirming that this setting applies to the editor and symptom. Note: The default is defined under /libs/settings/dam/cfm/jcr:content/autoSaveInterval. Do not edit /libs; use the supported configuration mechanism for an approved override. The new and original Content Fragment editors have different save behavior.
  7. If Author contains the intended latest content but Publish still shows the last published version, publish the Content Fragment. Then verify the content on both Author and Publish and review Version History for the resulting entry.

If the content changes on Author without an intentional edit, or unexpected versions continue after these checks, contact Adobe Support with the editor type, AEM version, relevant version-history timestamps, and steps to reproduce.

recommendation-more-help
experience-cloud-kcs-help-kbarticles