DocumentationExperience Cloud KCS

AEM Publisher displays incorrect content after SegmentNotFoundException following OS patching

Last update: October 27, 2026

Resolve an issue where an Adobe Experience Manager (AEM) Publisher instance displays incorrect or outdated content after OS patching because of SegmentNotFoundException errors. Clone a new publisher instance from a healthy one and update your load balancer.

Description description

After performing OS patching and restarting an AEM Publisher instance, the instance displays incorrect or outdated content. This can occur when repository segment errors lead to SegmentNotFoundException, which blocks content replication and causes some content or nodes to become unreadable or corrupted. Other publisher instances in the environment may continue to function normally and serve the correct content.

Environment

Adobe Experience Manager (AEM) Managed Services (all versions)

Symptoms

  • Publisher instance displays outdated or incorrect content.
  • Content replication to the affected publisher is blocked.
  • SegmentNotFoundException errors appear in logs.
  • Some content or nodes are unreadable or corrupted.

Cause

Repository segment errors resulting in SegmentNotFoundException can block content replication and cause content corruption. This issue can surface after an OS patch and restart, but is not necessarily caused by the patching itself.

Resolution resolution

Complete the following steps to resolve the issue.

  1. Validate repository health on the affected publisher instance by running an index consistency check to confirm index validity and identify any unreadable or corrupted nodes.

  2. Assess the extent of repository corruption. If corruption is widespread (many unreadable nodes), targeted node removal is not practical and could result in significant data loss.

  3. Restore from a healthy instance:

    1. Clone a new publisher instance from a validated, healthy publisher instance in your environment.
    2. Update your load balancer configuration to direct traffic to the new, healthy publisher instance.
    3. Remove the affected publisher instance from the load balancer to prevent serving incorrect content.

  4. Verify that the new publisher instance serves the correct content and functions as expected.

  5. Once validated, add the new publisher/dispatcher pair back to the load balancer.

Fix inconsistencies in repository when SegmentNotFound reported in AEM 6.x

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