Azure Logic Apps: How to Handle 429 Too Many Requests scenarios with Retry Policy?
I'm not sure how to approach I've looked through the documentation and I'm still confused about I recently switched to I tried several approaches but none seem to work... I'm currently working on an Azure Logic App that integrates with an external REST API, and I'm working with a `429 Too Many Requests` behavior when the API rate limit is exceeded. I want to implement a robust retry policy that can handle this behavior gracefully without failing the entire workflow. I have set up my Logic App to use an HTTP action to call the API, and I've configured the retry policy in the action settings to retry on failure. However, it seems to not be processing the retry correctly; instead, it just fails after the first attempt. Here’s my current configuration for the HTTP action: ```json { "type": "Http", "inputs": { "method": "GET", "uri": "https://api.example.com/data", "headers": { "Authorization": "Bearer {token}" } }, "retryPolicy": { "type": "exponential", "count": 5, "interval": "PT10S" } } ``` I also tried adding a delay before the retries by using a `Delay` action, but it still doesn't prevent the behavior from being thrown immediately. Instead of receiving a retry after the delay, I get the behavior message: `The request was unsuccessful due to too many requests. Please try again later.`. Could someone explain how to correctly implement a retry policy for HTTP actions in Azure Logic Apps specifically for handling `429 Too Many Requests` responses? Are there any settings I might be missing, or should I handle this in a different way? Any suggestions would be greatly appreciated! Thanks in advance! I'm coming from a different tech stack and learning Json. This is for a desktop app running on Windows 10. I'd be grateful for any help. I recently upgraded to Json 3.11. How would you solve this?