Can we prevent "Transactions that get too big will be committed automatically"

[Stuart Moore]

This page https://www.arangodb.com/docs/stable/transactions-limitations.html#rocksdb-storage-engine contains the worrying phrase

"Transactions that get too big (in terms of number of operations involved or the total size of data created or modified by the transaction) will be committed automatically."

There is some configuration detail there, but what worries me is there doesn't appear to be any way to know if this has happened, or to prevent it.

I have a use case where we need to rely on transactions being able to roll back - it seems like there's a potential for us to think we can roll back the transaction, but only be able to roll back the final part as the earlier bit has already been committed.

We'd prefer that the entire transaction was aborted if the limits were hit (so we could then look at tuning values) - is there any way to set this to happen?