Transaction cancellation
You can cancel transactions that take longer than expected to load. Canceling long-running transactions can help prevent excessive resource consumption.
- Sorting a large number of records by an unindexed string field.
- Grouping a large table on a field that has predominantly distinct values.
- Exporting all rows from a large table.
- Testing a poorly scripted business rule that has an infinite JavaScript loop.
Transaction cancel timer
During a long-running transaction, a timer and a cancellation option appear in an alert banner.
To cancel the transaction, select the Cancel button. The alert message displays when a transaction cancellation is in progress and when the cancellation is completed.
If a slow transaction completes successfully, the timer indicates how long it took for the transaction to complete.
Canceled transaction logs
Canceled transactions appear in the transaction log with CANCELLED appended to the URL. Transactions canceled by a user are logged differently from transactions canceled by transaction quotas. For more information about canceled transaction logging, see Canceled-transaction logging to a table. For more information about transaction quotas, see Transaction quotas.
Properties for transaction cancellation
Administrators can configure the behavior of the transaction cancellation capability using the following properties.
| Property | Definition | Location |
|---|---|---|
| com.glide.request_manager.active | Let users cancel long-running transactions (enabled by default). | Open the sys_properties table by navigating to All and entering sys_properties.list. |
| glide.ui.transaction.long_response.time | Delay in seconds before the cancel transaction button appears for a long-running transaction. | Navigate to and locate the field labeled Delay in seconds before the Transaction Cancel button is displayed for a long-running transaction. |