this is related to
KNL-809, KNL-808 and KNL-807 changes, where extra update events(content.upd.title, content.upd.access and content.upd.visibility) are posted, before the changed resource is actually committed.
So when certain event watcher classes receive those update event, and constructed the underlying resources, those resources could still have the pre-update attribute values, which would be confusing. Plus if there is any runtime exception prevents the resource commits, the "resource changed" events would then be invalid.
The suggested solution is to post those update event after resource is correctly committed/updated.