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