It was our own code that was causing the error. We had a SlingPostProcessor that was trying to access the resource. We now only proceed when no deletion modification is found.

I am getting an error when deleting a component:Caused by: javax.jcr.InvalidItemStateException: This item [/content/OBFUSCATED_PATH/responsivegrid/story_cards_componen_1364741682] does not exist anymoreAs you can see the resource DOES exists so I am not sure why I am getting this error. Any ideas?

Is there a way to prevent the afterchildinsert refresh listener from triggering when dragging components into the responsivegrid ('/libs/wcm/foundation/components/responsivegrid'):One possible solution would we overlaying this specific listener but I just one to know if there are other ways.

We are using the cloudservices link to Campaign in our setup but we are experiencing some issues. Our newsletter pagesare using the '/libs/mcm/campaign/components/campaign_newsletterpage' resourceSuperType (as described in the best pactices for email templates -> https://helpx.adobe.com/be_nl/experi...

Yes, when I enable it, it does trigger the other default replication for some reason. So it still seems like a bug to me.

Do you have any idea Jörg?

I investigated the empty ReplicationOptions thread using VisualVM:[Thread-3788] com.day.cq.replication.impl.ReplicatorImpl Setting up replication with options:ReplicationOptions{synchronous=false, revision='null', suppressStatusUpdate=false, suppressVersions=false, filter=null, aggregateHandler=null...

"Now 'msm-service' publish and invalidation request got triggered from the 'onmodify' trigger that was launched by 'pushonmodify' rollout. I believe this is what you mentioned as the problem statement. I'm not sure if this is a bug or expected functionality." Indeed I am not sure as well :S

When I navigate to http://localhost:4502/system/console/status-jstack-threaddump and repeat the scenario and look for 'Thread-1349' I find the following:"Thread-1349" #3948 daemon prio=1 os_prio=31 tid=0x00007fa7c8aeb000 nid=0x16107 waiting on condition [0x00007000112a1000]   java.lang.Thread.State:...

How have you configured the flush agent to be triggered automatically on modification as you have mentioned in the description? Is it via "On modification" checkbox under "Triggers" tab or something else?The dispatcher flush agent is the only agent that has the trigger 'On Modification' checked on i...