DocumentationExperience Cloud KCS

AEM as a Cloud Service: Intermittent missing Adobe I/O Page Version events

Last update: October 30, 2026

This article explains how to address an issue where Adobe I/O Page Version events are intermittently not delivered in AEM as a Cloud Service, causing downstream workflows such as page archival to miss certain page versions.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions prior to the August 2026 release)

Issue/Symptoms

  • Page versions are successfully created and visible in the Timeline console.
  • Adobe I/O Page Version events (aem.sites.page.versioned) are expected for each page version to trigger downstream workflows, such as archival.
  • For some page versions, no corresponding Adobe I/O event is received.
  • The issue is intermittent. Some versions trigger events, while others do not.
  • Downstream workflows that rely on these events may not process all page versions, leading to incomplete archival or automation records.

Cause

An internal error in the Sites Eventing page-event pipeline could disable the JCR listener for page events on an affected author pod, resulting in missing Adobe I/O Page Version events. This issue was addressed in a product release in August 2026.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Confirm your AEM as a Cloud Service environment is running a release from August 2026 or later, which includes the fix for intermittent missing aem.sites.page.versioned events.
  2. After the fix is deployed, create new page versions in your environment.
  3. Monitor the Adobe I/O Runtime/Journaling to verify that a corresponding aem.sites.page.versionedevent is received for each new page version.
    • For each new page version, check both the Timeline console and the Adobe I/O event stream for matching entries.
  4. Continue monitoring event delivery over several days to ensure stability, as the issue was previously intermittent.
  5. If missing events are observed after the fix, collect affected page paths, version numbers, and timestamps for further investigation.
  6. If the problem persists, open a new Adobe Support case with detailed examples (page path, version, creation time, and event logs).
recommendation-more-help
experience-cloud-kcs-help-kbarticles