Transaction revision conflict

The transaction cannot commit against its stated revision. A later transaction touched an overlapping path, or the supplied base revision is ahead of the store. Journal restoration also rejects a transaction whose result revision is not newer than the store. A rejected transaction leaves no committed changes.

#Common causes

• A client edited a field using a revision from before another edit to that field or record.
• A revision from another store was reused, or journal transactions arrived out of order.

#Fixes

• Read session.status, inspect the current entity with ara_inspect and reconcile the conflicting value before retrying ara_apply against the current revision.

• Use ara history to identify the transaction named in the message; for journal replay failures, investigate the accompanying ARA1905 instead of resubmitting out-of-order transactions.

• Code: ARA1501

• Constant: STALE_BASE

• Reported by: ara-ops