Atomic operator to prevent DB lock issues / race conditions?

According to the AI Agent in Bubble: Where you need a stored total, use Bubble’s “Make changes to a Thing” with the += (add to) operator on the parent’s balance. Bubble applies it as an atomic increment, which avoids lost updates.

Is this true? I wasn’t aware Bubble had this functionality and in order to not lose fast-paced updates to account “balance” fields, I currently do a crazy workaround with a Redis microservice and polling/updating separately intermittently.

But if this is true, I’d love to migrate to this. Any confirmation this is true and could handle high ops updates? Nothing in the docs.

New workflow engine solves a lot of this I believe

can you confirm that += solves for DB locking and race condition issues?

In my experience that does not work 100% of the time.

This isn’t an operator, it’s hallucinating