If you have soft delete enabled, deleting a row will set the column associated with the 'deletedAtKey'. Following this with a forced delete will not result in the row being deleted. The following SQL is generated on PostgreSQL:

DELETE FROM "MyTable" WHERE ("MyTable"."deletedAt" IS NULL OR "MyTable"."deletedAt" > ($1)) AND "MyTable"."id" = ($2) [0x00022aab9bdf99ee (TIMESTAMP), 24 (BIGINT)]

where the timestamp ($1) is after the deletedAtKey column value. The fix may be as simple as changing '>' to '<'. There is currently not a unit test for this case.