Page Published details getting updated in Timelines of Page edit after content updated on Page AEM6.5 on-Premise | Community
Skip to main content
Level 3
November 5, 2024

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

  • November 5, 2024
  • 2 replies
  • 851 views

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.

 

2 replies

Harwinder-singh
Community Advisor
Community Advisor
November 5, 2024

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

Level 3
November 5, 2024

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)?

Harwinder-singh
Community Advisor
Community Advisor
November 6, 2024

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

kautuk_sahni
Community Manager
Community Manager
November 11, 2024

@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
Level 3
November 11, 2024

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.