Azure Logic Apps · Throttling
429 - Too Many Requests
A 429 in Azure Logic Apps means the number of requests exceeded the rate that the logic app resource, the connector or the destination service can handle over a specific amount of time. Limit concurrency, spread requests over more connections, or move to batch or webhook patterns. For logic app resource throttling, limit the number of workflow instances that run at the same time, enable high throughput mode, turn off the trigger's Split On setting, or refactor actions into smaller workflows.
VerifiedLast verified
01Error text
HTTP 429 Too Many Requests02Likely causes
- The logic app resource exceeds its throughput limits.
- A connector exceeds its own throttling limits. For Consumption workflows, throttling happens at the connection level.
- The destination service or system called by the connector has stricter throttling limits.
03How to fix it
- For logic app resource throttling, limit the number of workflow instances that run at the same time, enable high throughput mode, turn off the trigger's Split On setting, or refactor actions into smaller workflows.
- For connector throttling, set up multiple connections for a single action or a different connection for each action, or reduce the concurrency of the For each loop.
- For destination throttling, create individual workflows that each handle a single operation, set up batch processing, or use the webhook versions of triggers and actions instead of the polling versions.
iNotes
Where a trigger or action supports a retry policy, it retries requests that result in a 408, 429 or 5xx response.
04Official documentation
→Related errors
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Azure Logic Apps work:Open Azure Logic Apps jobsAzure Logic Apps rates and salaries