Response Returned by a REST Table API That's Cancelled Due to Exceeding a Transaction Quota RuleSummaryResponse Body of a REST API Transaction Cancelled Due to Exceeding a Transaction Quota Rule If a REST API transaction (request) is cancelled by a Transaction Quota Rule due to exceeding the time specified in that rule it will send the following at the end of the HTTP response body: "error": {"message": "Transaction cancelled: maximum execution time exceeded","detail": "Transaction cancelled: maximum execution time exceeded Check logs for error trace or enable glide.rest.debug property to verify REST request processing"},"status": "failure"}Also, it's likely that the payload will not be formatted as expected since its transmission was cut off by the Transaction Quota Rule, as shown in the image below. HTTP Response Code of a REST API Transaction Cancelled Due to Exceeding a Transaction Quota Rule If the transaction cancelled by a Transaction Quota Rule was processed (even partially) on an API_INT semaphore it will return a HTTP 200 response. BUT if the transaction gets caught in a semaphore queue, and never gets to run on a semaphore before hitting the timeout, then the response will be HTTP 500. Note that a transaction that gets rejected because the semaphore queues are already full (max queue length 50 on the OOB API_INT semaphores) will get a HTTP 429 and will never have a chance to run so never hit the Transaction Quota Rule. Related LinksTransaction Log[syslog_transaction] Entries In the Transaction Logs, look for a Transaction where the URL begins with "CANCELLED:" Node Log Entries to Check For These are example node logs (see Node Log File Downloader) that indicate a Transaction Quota Rule was exceeded: 2020-08-24 17:06:36 (028) glide.quota.manager SYSTEM Quota exceeded for REST and JSON Catch All, requesting cancel 2020-08-24 17:06:47 (251) Default-thread-1 D0C0001ADBBED8509ED75818489619F2 txid=c6f2c09edb3e WARNING *** WARNING *** Transaction cancelled: maximum execution time exceeded