Due to some refactoring in the Oracle event processing logic, if the XID (transaction id) does not have any sequence details on a mining step, there is a branch of logic that mistakenly logs:

Cannot undo change on table '{}' since event with row-id {} was not found.