In attempting to publish content fragments there are a couple of pieces of content that cause the replication queue to be blocked with this error. Caused by: org.apache.jackrabbit.vault.packaging.PackageException: Error creating/updating node /content/dam/.../jcr:content at org.apache.jackrabbit.vau...

None of our custom code is adding these fields. 

How do you look for incompatible node types? Everything looks on the up and up in CRXDE Lite. 

I stumbled on this while searching for an answer as to why some of our content isn't replicating and throwing a similar error. What does it mean if you get a "Parent node not found" error? I've never seen this before. Especially not with content that clearly has a parent node. 

I'm curious what the cause of this could be. During replication we're seeing this error in our publish logs. In CRXDE Lite we show that the field "cq:isDelivered" is present. As far as I can tell we're not manipulating the JCR store in code to change this value. I'm not sure that we've changed it in...