Well, for me that feels like a bandaid for a different problem...

Why don't you use the replication API for this? 

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...

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

Can you please share the ticket ID in private with me?

That's a nice writeup, thank you! I have debugged a few issues like this already, and it is indeed a common issue, especially if the exception is only happening sporadically. That means that you have a broken version in the dispatcher cache, but when a request bypasses the cache (e.g. by adding a qu...

can you post the complete exception including the relevant parts of the stacktrace, so we can actually find out what went wrong here? the exception message alone is not enough. But also: can you please raise a feature request here and describe your usecase a bit better, especially why you want to sy...

To help here further, one would need to understand your implementation details much better, especially on which system this exception is written. Are these 2 authoring instances part of the same AEM CS program? In that case, would the Content Copy tool work for you? 

You mean why want to built author-to-author replication between 2 AEM CS Prod environments?