MID Server error Too Many Requests with code 429Issue The MID Server returns the error Too Many Requests with code 429 when communicating with the instance. Symptoms The following errors appear in the MID Server logs: ECCQueueMonitor.5 WARNING *** WARNING *** Method failed: (https://<instance-name>.service-now.com/ecc_queue.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.1 429 Too Many Requests with code: 429 ECCQueueMonitor.5 SEVERE *** ERROR *** getRecords failed (Method failed: (https://<instance-name>.service-now.com/ecc Release All supported releases Cause The API_INT is one of the semaphores that MID Servers use when communicating with the instance. When the API_INT semaphores are exhausted and the queue depth reaches the maximum queue depth, the instance returns the error Too Many Requests with code 429 to any MID Server client that attempts communication. Because no semaphores are available, the instance cannot receive any input or heartbeats from the MID Server. Resolution The solution depends on what keeps the semaphores busy. To check whether the API_INT semaphores are exhausted: In a browser window, go to .service-now.com/stats.do.Search for API_INT.Check that no semaphores are available and that the queue depth equals the maximum queue depth An exhausted API_INT resembles the following example. API_INT Available semaphores: Queue depth: 50 Max queue depth: 50 0:<sys_id> #<transaction_number> /api/now/table/sys_audit (API_INT-thread-2) (2:05:30.388) 1:<sys_id> #<transaction_number> /api/now/table/sys_audit (API_INT-thread-4) (1:57:30.087) 2:<sys_id> #<transaction_number> /api/now/table/sys_audit (API_INT-thread-1) (1:55:29.678) 3:<sys_id> #<transaction_number> /api/now/table/sys_audit (API_INT-thread-3) (1:28:03.004) In this example, long queries on the sys_audit table use all available API_INT semaphores. The long-running queries can be on a different table. For immediate relief: Go to User Administration > All Active Transactions.Find the long-running transactions that keep the semaphores busy.Confirm with the team responsible for the transactions that ending the transactions does not cause any issues.End the transactions to free up the semaphores. For long-term relief: Contact the team responsible for the long-running transactions and work with the team to improve the transactions.