Am 20.11.15 um 09:10 schrieb Roll, Kevin: > OK, allow me to broaden the question. We are getting mysterious repository > corruption as previously detailed. I'm fairly certain that this is related to > a task I have that scans Resources and sets some node properties but I can't > pin down what I might be doing wrong. Are there any common mistakes that > might cause the "Item does not exist anymore" exception? I can describe my > code in more depth if that would help, but it is rather involved.
This can have several reasons. Usually when I'm seeing this it happens that concurrent resource resolvers are involved. While for example one resolver traverses a tree, another one is modifying it. Carsten
