Where do these calculations happen? On author? In that situation the replication status is accurate. It's just that the information on publish is not accurate, but at that point you don't really need it at all.

 @TimothyJ wrote: I am an admin and Well, you might have an admin role in your organisation, but your are NOT the "admin" of the AEM instance (meaning that role you get when you use "admin/admin" on your local SDK instance). For that reason you cannot impersonate into other users unless these users ...

The dispatcher is not involved here, this error message comes from AEM directly.

I wrote a 2 blog posts in the context of AEM CS backups and how you should use them: AEM CS backups are not for archival. And in my blog post I raised a number of questions why in one of my consulting projects I did not considered backups as a proper solution for an AEM on prem setup.And most of the...

I checked briefly, and on that day a single instance was affected a few times by this issue. Nothing in the days before and after, and it's also not a common issue which I am aware of. I would consider this a one-time glitch.

I wonder why need this logic on publish at all; because by definition all content on publish is already published. Or do I miss something? Also, the replication status information is added after the replication has taken place; and the replication process itself replicates the content fragment as it...

This is the not the correct answer, as this IP range might change without further notice. If you need your AEM environment make calls to an external service, and these requests must come from a specific IP/small set of IPs, then use the Dedicated Egress IP solution, as correctly suggested by @Mahedi...

Please the documentation on Apache Oak Restriction Management: https://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html#rep-glob-details-and-examples The examples are quite helpful.

What type of event listener do you use? JCR Observation listener or Sling ResourceChange listener? And can you share the event handler you implemented?

what would like to store in that field? And what should this information get used for?