Concurrency issues occur when the exact same record is updated and saved by two different sessions of Argos Vault or Bailment
If this occurs the following Concurrency Error dialog will display for the user who tries to save the record last:
[Button] | Explanation |
| The user will be returned to the dialog and the data will not be changed
This allows for changes to be noted before they are lost |
| The following dialog will be displayed
 to return to the Concurrency Error dialog
 to return to the Browse
This session's changes will be lost and the record displayed in the Browse will be the latest version in the database (as updated by the other session) |
| The following dialog will be displayed
 to return to the Concurrency Error dialog
 to return to the refreshed dialog, which will be updated with the changes from the other session
The required changes can now be re-entered |
Process Concurrency
This form of error reporting is used by the following processes:
- Bailment Interest Posting
- Bailment Write Off Interest
- Bailment Retail Contra posting
If a process is being run, the concurrency error will be similar to:
"There were some errors during the Processing:
Posting failed for Account .... Another User has modified the account"
In each case a list of accounts that had concurrency issues is listed. The routine may be run again to post to these accounts.