Hi @JesusTheHun . We do try to detect if a non-transactional concurrent write has been made to a document at the point it is unstaged, using techniques including CAS. As you say we cannot fix the situation (we are committed here, and cannot rollback the transaction) - but we can warn the user this is going on.
Each SDK will differ in how it raises these issues to the user. The Java SDK for instance will both log them, and raise events you can subscribe on - see these docs for more.
It’s best-effort though, as there are some situations where we do not have enough information to reliably know if this has occurred.