I can't speak for others, but Magma doesn't silently restart any transactions, ever. That example sounds like mismanagement of a dirty-read situation.
I forgot one exception I just recently added. It checks for conflicts when building an index, to ensure all objects of the MagmaCollection will be indexed correctly.