Overview
If a user creates an object in M-Files, leaves it checked out, and then performs an "Undo Checkout" operation on the object, this causes an "Object Destroyed" event to be logged in the vault event log.
While undoing checkout for an object in version 1 technically involves the destruction of that object, this can cause confusion and concern, especially when the user may not have permission to destroy objects.
This issue can become more prevalent when an integration creates objects in the vault and encounters problems when attempting to check in the newly created object. The cancellation of that transaction will cause the same event in the vault event log. The difference is that this use case can cause many more events to be written.
