Offer component missing in AEM Preview environment after updates in Author
In Adobe Experience Manager (AEM), offer components that you add or update in Author don’t appear in the Preview environment. The issue often affects specific pages while other pages continue to display updated content as expected. No error messages appear, but Preview shows missing or outdated offer components, which affects content validation before publication. To fix this issue, verify the page content and API response, check Preview or backend-for-frontend caching, and republish the affected page.
Description description
Environment
- Adobe Experience Manager (AEM), all versions
- Decoupled/headless Preview environments (for example, custom frontend applications consuming AEM APIs)
Issue/Symptoms
- Updated or new offer components are visible in AEM Author but not in the Preview environment.
- Other pages may update as expected; the issue is specific to certain pages.
- No explicit error messages are shown.
Cause
The most common cause is caching in the Preview environment or its backend-for-frontend (BFF) layer, which may serve stale API responses. This is not typically an AEM Author or Publish replication issue.
Resolution resolution
Follow these steps to resolve the issue:
- Verify that all intended offer components are present and published in the AEM Author environment.
- Use CRX/DE or the AEM Sites console to confirm that the
jcr:contentnode for the affected page contains the correct components. - Identify the API endpoint that the Preview application uses to fetch content. This endpoint is often a custom or headless endpoint. Consult your frontend or backend teams if you’re unsure.
- Access the endpoint directly with a browser or API tool, and verify that the JSON response includes all expected offer components.
- Determine whether the Preview environment or its backend-for-frontend layer caches API responses. Clear the cache or reduce the cache time-to-live to fetch fresh content. If the implementation includes custom cache invalidation logic, verify that the logic is enabled and functioning.
- Make a small, identifiable change to the affected page in Author, such as editing text or rearranging components. Note the change time and monitor when the Preview environment displays the update.
- Review the AEM and Preview or backend-for-frontend logs to trace the change propagation.
- If the issue persists, update and republish the page or its
jcr:contentnode to force a refresh. - Ask your frontend or backend teams to review the integration and caching logic. Verify that the Preview application calls the correct AEM endpoints and doesn’t serve stale content from its cache.
- Verify that all offer components appear and display current content in the Preview environment.