Changing Transaction Command Timings
- Last UpdatedFeb 07, 2022
- 2 minute read
In a Global project only, the Administrator at each location can override various default values that affect the processing of transaction commands. For example, the Administrator can change the maximum length of time spent trying to send a command.
To change these default values, from the main Admin menu bar, select Settings>Transaction Timings to display the Transaction Command Timings form:

The Event Loop is common to all locations. It is the time, ranging from 1 second to 5 minutes (300 seconds), between the execution of each operation arising from a command. The recommended Event Loop is 5 seconds.
The Timings to Locations panel displays the timing values for commands issued from a specific Location.
Use the Location list to specify the location for which the timing values will be displayed. The list shows all the locations to which the current location (the location at which the Administrator is using this form) has a direct connection, that is, the parent and immediate children (if any).
The Timeout is the maximum period of time spent trying to send a command.
Note:
Using a short timeout value can cause some operations to fail (e.g. Claims and Flushes).
Retries is the maximum number of times that an attempt is made to send a command.
The Interval is the delay between retries.
Resend is the delay before resending a command that has already been sent. This is a failsafe.
Click Apply to set the event timings for the selected Location to be the values displayed currently.
Click Defaults to display the default settings for the selected Location.
Click Current Settings to display the current settings for the selected Location - these may be different to the default settings.