Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.
SOLVED

Publish content is not reflected in live site

Avatar

Level 2

The changes that are made in the author is reflected in Preview site but when published to live, they were reverted back to the old content shortly after it was pushed live. Tried clearing the cache, the same issue.. the changes are reflected but after some time itis reverted back to old content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hello @Abbirami ,

Do you have multiple dispatcher servers and multiple publish servers?

It sounds like some of them are not in sync when you publish a page/asset.

 

An explanation of "reverting the change to old content" that I have experienced is when,

1. Some publish servers are not receiving the content when other publishers are. If you are using replication agents then it's worth checking if the replication agent is not blocked and not timing out.

Test individual test server for latest content after publication.

2. Some dispatcher servers are not having the cache cleared in time. Meaning is a possibility of a race condition where published content, cache flush and accessing new content either overlap or take very long, causing the old page to cache on some servers. Reviewing dispatcher cache flush behavior will help here.

Test individual test server for latest content after publication.

3. If you use a CDN, the irregular caching only increases, as the CDN might take the content from one of the dispatcher servers with either latest content or old content, causing some times seeing old content and other times new.

 

Start debugging inside-out starting with publisher, then dispatcher and then CDN.

 

If you find this helpful please let us know or if you find something else caused the issue please post the answer for benefit of someone who might be in a similar situation.

 

 

Thanks,

Preetpal 

View solution in original post

6 Replies

Avatar

Community Advisor

@Abbirami in general no concept of revert back I have ever heard.. mostly could be your Publisher-Dispatcher config issue.. how many Pub-Disp combinations you have? Did you check latest content on all pubs? How's your Dispatcher cache looks like? Do you use CDN?

Avatar

Community Advisor

Try replicating the issue in a non PROD environment.

Also, try to get logs for the live environment and see if you can find something there.

Avatar

Correct answer by
Community Advisor

Hello @Abbirami ,

Do you have multiple dispatcher servers and multiple publish servers?

It sounds like some of them are not in sync when you publish a page/asset.

 

An explanation of "reverting the change to old content" that I have experienced is when,

1. Some publish servers are not receiving the content when other publishers are. If you are using replication agents then it's worth checking if the replication agent is not blocked and not timing out.

Test individual test server for latest content after publication.

2. Some dispatcher servers are not having the cache cleared in time. Meaning is a possibility of a race condition where published content, cache flush and accessing new content either overlap or take very long, causing the old page to cache on some servers. Reviewing dispatcher cache flush behavior will help here.

Test individual test server for latest content after publication.

3. If you use a CDN, the irregular caching only increases, as the CDN might take the content from one of the dispatcher servers with either latest content or old content, causing some times seeing old content and other times new.

 

Start debugging inside-out starting with publisher, then dispatcher and then CDN.

 

If you find this helpful please let us know or if you find something else caused the issue please post the answer for benefit of someone who might be in a similar situation.

 

 

Thanks,

Preetpal 

Avatar

Community Advisor

@Abbirami 

 

1. Assure that the content was successfully published from Author to Publish. Please check replication queue.

2. If its an AMS or an on-premise instance, try accessing the content via (ALL) Publish instance's URL directly

3. Perform all validation via Browser's Incognito or Private Mode

4. If its an AMS or an on-premise instance, Assure that the cache on the dispatcher is deleted (all linked dispatcher)

5. try accessing the content via (ALL) Dispatcher URL 

6. Assure the content is not cached on CDN.

 

You can also analyze, if the results are coming from a cache by following https://techrevel.blog/2023/09/05/exploring-aem-request-and-response-headers-analysis-of-browser-cdn... 


Aanchal Sikka

Avatar

Employee Advisor

Is this an AEM as a Cloud Service instance or running on-prem / in AMS?

Avatar

Administrator

@Abbirami  Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni