Error 429 on When a New Email Arrives Outlook Trigger

(1) Share

Report

Posted on by CU20031603-0

Body Output :

{
  "status": 429,
  "message": "Too many requests from Identifier:7ab7862c-4c57-491e-8a45-d52a7e023983 under category:throttle.aad.ags.subscriptionservice.app.extended2. Please try again later.\r\nclientRequestId: 51aa0dce-b7f2-4653-bbde-ac12033325d3\r\nserviceRequestId: 59f8ec06-791d-4787-9b6a-56bdc3d1a2cd",
  "error": {
    "message": "Too many requests from Identifier:7ab7862c-4c57-491e-8a45-d52a7e023983 under category:throttle.aad.ags.subscriptionservice.app.extended2. Please try again later."
  },
  "source": "172...."
}

Hi,  I share a power automate workflow with Admin to ensure connectors work properly. It tests as working but the runs do not show up despite working well for months. However, it gave a 429 error code which means too much traffic. The flow creates a planner task any time I get an email from a client and it was a test. It does not get more than 20 emails a day but I plan to replicate it for a larger department process. I don't see anything that should have triggered the error. 

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Haque 3,653 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @CU20031603-0,

Let's scrutinize the error:

Status: 429 Too Many Requests

Message: “Too many requests from Identifier … under category: throttle.aad.ags.subscriptionservice.app.extended2. Please try again later.”

Meaning: Your flow or app has hit Azure Active Directory (AAD) throttling limits. The connector is making more requests than allowed in a given time window.

Impact: Requests are being blocked until the throttling window resets.

So possible reason this happens:

High request volume: Too many calls to Office 365/AAD in a short period.

Loops or bulk operations: Flows iterating over large datasets without batching.

Multiple users or flows: Shared connectors hitting tenant‑wide limits.

Background retries: Failed runs retrying automatically, adding load.

And let's mark/make sure which one is common for you from the above point.

Several things we need to try:

1. Reduce request frequencies - you may add delay (5-10 sec) or relinquish loops to concurrency control. Batching can be on more option (not squentially, in a batch)

2. Flow optimization is very important - avoid multiple Get items action in a loop, utlize Filter arrya/Select to minimize actions.

3. Introducing child flows is wise when block becomes bigger - break large jobs into smaller scheduled runs.

4. Tenant limits - please work with your Power Platform admin to review throttling policies.

5. Finally, sometimes throttling is evanescent (short-lived), requests will succeed once the window resets. Also, don't forget to add retry policies to handle transient 429 errors gracefully.

Please let me know which one worked for you.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Haque 3,653 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CU20031603-0,

I was just following up, where my clues helpful? Still facing this issue?

Was this reply helpful? Yes No