--- sourceDocument: Brazil ServiceNow AI Platform Administration sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Transaction quotas # Transaction quotas {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Transaction quotas Transaction quotas enable administrators to define policies that limit the resource consumption of various transaction types in the ServiceNow platform. By enforcing these quotas, poorly performing queries and scripts that could monopolize system resources are automatically canceled. This mechanism helps maintain overall system performance and availability by preventing any single transaction from adversely affecting others. Show full answer Show less The Transaction Quotas feature is active by default on all new and upgraded instances, ensuring immediate protection against excessive resource consumption. ## How Transaction Quotas Work * The Quota Manager operates as a background thread that monitors active transactions and enforces quota rules. * It retrieves the list of currently running transactions and evaluates each against defined quota rules based on specified conditions. * When a transaction exceeds any quota limitation, it is canceled immediately to free system resources. * The order in which quota rules are evaluated is controlled by an "Order" field, with lower-order rules checked before higher-order ones. * The Quota Manager continually re-evaluates transactions if their state changes or if quota rules are updated. * Transaction cancellations are logged for administrative review. ## Transaction Cancellation and Logging When a transaction surpasses the maximum allowed execution time defined in a quota rule, it is canceled and the user receives a notification explaining the cancellation reason. All such cancellations are recorded in the **Transaction Cancellation Log**, accessible via: *All \> System Logs \> System Log \> Transaction Cancellation Log* This log helps administrators identify transactions that frequently consume excessive resources and adjust quota policies accordingly. ## Transaction Cancellation Messages * **maximum execution time exceeded:** Indicates cancellation by the glide.quota.manager thread due to quota violation. * **canceled by other transaction:** Indicates cancellation by the session thread that initiated the transaction, not by the Quota Manager. * **canceled by user request:** Indicates manual cancellation by the user via the interface. To specifically find transactions canceled due to quota breaches, search the log for entries containing "maximum execution time exceeded". Transaction quotas allow you to define a quota policy for different types of transactions. A transaction quota cancels any transaction in violation of the policy and notifies the user of the cancellation. Administrators can set transaction quotas to prevent poorly performing queries and scripts from consuming system resources. This ensures that no transaction consumes enough resources to prevent other transactions from running. Administrators can also view cancellation log messages to identify transactions that might consume excessive resources. The Transaction Quotas plugin is active by default on all new and upgraded instances. ## How transaction quotas work Transactions use the Quota Manager, which is a background thread that cancels transactions according to transaction quota rules. The Quota Manager performs the following actions. 1. Obtains a list of active transactions, similar to the list under User AdministrationActive Transactions. 2. Cycles through each transaction and checks all quota rules with conditions matching the transaction. The first occurrence that exceeds any of the quota limitations triggers a transaction cancellation. If a transaction changes or there is a new quota rule, the Quota Manager re-evaluates the transaction. Note: The Order field on a quota rule affects the order in which the quota rules are checked. The Quota Manager checks lower-order rules first (for example, order 80 before order 90), but ultimately checks all rules. This might have marginal performance implications, depending on the conditions of the rules involved. 3. Cancels the transaction if it has been running longer than the specified quota maximum. 4. Logs the running transactions. 5. Sleeps until the next heartbeat, which is controlled by the glide.quota.manager.heartbeat [system property](https://www.servicenow.com/docs/UueqgciKi5O5b5~Vxdrrcg "An administrator can add the following system properties to manage transaction quotas."). {#c_TransactionQuotas__ol_lwr_pr1_rp} ## Transaction cancellation from exceeded quotas {#c_TransactionQuotas__section_g3v_3j4_gfc} When a transaction runs longer than the maximum duration specified by a quota rule, the user is notified of the cancellation and the reason. Additionally, a warning is logged in the Transaction Cancellation Log whenever a transaction is cancelled due to exceeded quotas. To view the Transaction Cancellation Log, navigate to AllSystem LogsSystem LogTransaction Cancellation Log. ## Transaction cancellation examples Transactions can be canceled for more than one reason. Look for the following indicators. * maximum execution time exceeded: This message appears when the glide.quota.manager threads cancels the transaction. * canceled by other transaction: This message appears when the transaction was canceled by the session thread that initially issued it, and not by the glide.quota.manager thread. * canceled by user request: This message appears when the user selected the red X button to cancel the running transaction. {#c_TransactionQuotas__ul_eyp_dk1_ts} If you are looking for transactions that were canceled by glide.quota.manager, search for the \[Message\] \[Contains\] \[maximum execution time exceeded\] combination. For example: Cancelling transaction /home.do - Default-thread-11.0 (maximum execution time exceeded): Thread Default-thread-11.0 (Default-thread-11.0, F530DD111B11111111FC031767DA158E), after 30000ms . *[\>]: and then