Expand my Community achievements bar.

Page Published details getting updated in Timelines of Page edit after content updated on Page AEM6.5 on-Premise

Avatar

Level 3

Hi All,

We have production author where we see issue with timelines details issue upon page edit as "page published" timelines details has been updated when ever page edited, attached screenshot for reference.

Kindly share your suggestions on this "replication-service" user related details to do further investigation why "page published" timeline details getting updated whenever page edited.

 

Attached screenshot for reference.

rajukomari_0-1730820406815.png

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

6 Replies

Avatar

Community Advisor

@raju-komari  replication-service is a system user that is used for replication of content in AEM. 

Avatar

Level 3

Hi Harwinder, 

Thanks for the update, is it some replication workflow getting called on each page edit? because of this, Page timeline showing as Page Published even page not published ( only page edited)?

Avatar

Community Advisor

@raju-komari  Yes, it looks like some workflow or event listener is invoking this replication. You can check the AEM logs to verify this.

Avatar

Level 3

Hi Harwinder,

Thanks for the update.

Unfortunately, we could not find any logs related to this page replication after validating all logs in the production author.

Need to validate from code level(front end/back end) if anything get triggered on page edit.

Keep you posted once we get the any information related to this after validation.

Thank you.

  

Avatar

Administrator

@raju-komari Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!



Kautuk Sahni

Avatar

Level 3

Hi Kautuk,

I am unable to find the reference to this issue from our entire code base, Still we are doing investigation and keep you posted.

Kindly share your suggestions/comments as well to do further investigation with different options because not getting exact leads for this issue from our codebase.

Thank you.