Queued updating replication
Deprecated features should not be used in new applications.Updatable subscriptions including immediate updating and queued updating with snapshot and transactional publications.Therefore, it didn't undergo extensive QA, and comes with the same warnings as an official hot fix: THE HOT FIX PACKAGE IS PROVIDED “AS IS” AND WITHOUT WARRANTY OF ANY KIND, INCLUDING WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY, LACK OF VIRUSES, TITLE, NON-INFRINGEMENT, ACCURACY OR COMPLETENESS OF RESPONSES, RESULTS, LACK OF NEGLIGENCE AND/OR LACK OF WORKMANLIKE EFFORT. ADOBE RECOMMENDS THAT THIS HOT FIX PACKAGE BE USED FOR DEVELOPMENT PURPOSES.ADOBE DOES NOT WARRANT AGAINST ANY BUG, ERROR, OMISSION, DEFECT, DEFICIENCY, OR NONCONFORMITY IN THE HOT FIX. IF YOU MUST APPLY THIS HOT FIX PACKAGE TO A PRODUCTION SYSTEM, YOU SHOULD THOROUGHLY TEST YOUR APPLICATION.When an updating subscription to a transactional publication supports failover from one updating mode to another, you can programmatically switch update modes to handle situations when connectivity changes for a short period of time.The update mode can be set programmatically and on demand using replication stored procedures.This feature remains supported in versions of SQL Server from 2012 through 2016.
When published data is changed at either the Publisher or the Subscriber, the row receives a new globally unique identifier (GUID) to indicate that a new row version exists.By updating the publication with the GUID from the transaction, you have matching row versions in the publication and in the transaction.If the old GUID stored in the transaction does not match the GUID in the publication, a conflict is detected.Quickest way to do this is to use CRXDE Lite ( and delete the node: /var/eventing/jobs/assigned/%INSTANCE-SLING-ID%/%REPLICATION-AGENT-FULL-ID% So for example with the default publish agent: /var/eventing/jobs/assigned/e23dd09d-83f1-4735-a77c-394df479214c/cq.publish Note this is considered as an exceptional workaround action In versions of AEM 5.4 and earlier, replication queues can sometimes be polluted by entries that cannot be removed through the OOTB Clear Queue link.In this case, you can use the Replication Queue Cleaning tool attached here.