Power automate workflow suddenly run failed, error code 504 and 429

Question

Anyone can help

Here is log:

{

"statusCode": 504,

"headers": {

"Pragma": "no-cache", 

"Cache-Control": "no-store, no-cache", 

"Set-Cookie": "", 

"x-ms-datasourceerror": "True", 

"x-ms-request-id": "", 

"Strict-Transport-Security": "", 

"X-Content-Type-Options": "nosniff", 

"X-Frame-Options": "DENY", 

"Timing-Allow-Origin": "\*", 

"x-ms-apihub-cached-response": "true", 

"x-ms-apihub-obo": "false", 

"Date": "Wed, 07 Jun 2023 06:56:55 GMT", 

"Content-Length": "521", 

"Content-Type": "application/json", 

"Expires": "-1" 

},

"body": {

"error": { 

  "code": 504, 

  "source": "", 

  "clientRequestId": "", 

  "message": "BadGateway", 

  "innerError": { 

    "status": 504, 

    "message": "Request to Graph API has timed out.", 

    "error": { 

      "message": "Request to Graph API has timed out." 

    }, 

    "source": "" 

  } 

} 

}

}

Another error cord 429

{

"statusCode": 429,

"headers": {

"Pragma": "no-cache", 

"x-ms-request-id": "", 

"Strict-Transport-Security": "", 

"X-Content-Type-Options": "nosniff", 

"X-Frame-Options": "DENY", 

"Timing-Allow-Origin": "\*", 

"x-ms-apihub-cached-response": "true", 

"x-ms-apihub-obo": "false", 

"Cache-Control": "no-store, no-cache", 

"Date": "Tue, 06 Jun 2023 05:48:39 GMT", 

"Content-Length": "370", 

"Content-Type": "application/json", 

"Expires": "-1" 

},

"body": {

"status": 429, 

"message": "Too many requests to Graph API. Please try again later.", 

"error": { 

  "message": "Too many requests to Graph API. Please try again later." 

}, 

"source": "" 

}

}

This workflow is keep check sharepoint list if there an new item created, data update from sharepoint list to sharepoint excel table, before 10 days are ran smoothly, after June 5 afternoon 5:35pm, got run failed up to now still not return normal.

Answer 1

Dear Ryan,

Based on the error message "Too many requests to Graph API. Please try again later.", it seems that too many requests are called in the flow which may break the limitation of the flow mentioned in Limits and configuration - Power Automate | Microsoft Learn and causes the error of the flow.

You may run turn off the flow temporarily and run the flow later to see the result.

You may also check whether there are some running processes in the flow history and cancel them manually first.

Meanwhile, you can save the flow as a new flow, delete the original one and run the new flow in the test mode to see the result as well.

Solved: 429 Too Many Requests Error - Power Platform Community (microsoft.com)

Welcome to share any updates when you have time if you need further help on this issue.

Thanks for your effort and time!

Sincerely

Cliff | Microsoft Community Moderator

Answer 2

Thanks for you reply, but my workflow just a simple workflow (only four step), and up to now record not over 1000 row, below is capture screen of my workflow and run history, do you think that my workflow was restricted by limit? how to break the limitation? my O365 license is E5, please advise need to add which license for break the limitation? and pls also provide license cost to me, thanks.

Answer 3

Dear Ryan,

Thanks for your updates and letting us know the current situation in your environment.

The error may occur when the flow is triggered many times and performed too many executions in a short time frame on a model.

I suggest you follow the steps in Too many requests error in Power Automate - AI Builder | Microsoft Learn and set the limit from the solution to see if the issue disappears in your environment. If yes, that limit may be the root cause in your environment.

Welcome to share any updates when you have time if you need further help on this issue.

Thanks for your effort and time!

Sincerely

Cliff | Microsoft Community Moderator

Answer 4

Dear Cliff,

Thanks your replied to me, I follow the settings on Concurrency Control to set from 25 (default) to 4, have improvement to run my workflow, but still have random got the issue, "BadGateway", it look like DNS issue, then workflow running long time on “Add a row into table”, attached run history for you reference. looking forward to your reply. thanks.

![](https://learn-attachment.microsoft.com/api/attachments/5990320b-1737-41ce-bcd9-53d744cd1af9?platform=QnA"https://learn-attachment.microsoft.com/api/attachments/a69a03db-1541-4654-b8f0-293cb30cd8af?platform=QnA" rel="ugc nofollow">![](https://learn-attachment.microsoft.com/api/attachments/a69a03db-1541-4654-b8f0-293cb30cd8af?platform=QnA

Answer 5

Dear Ryan,

Thanks for your updates and kindness.

If it is convenient, could you save the flow as a new one, remove the old affected flow, set the Concurrency Control value to 1 and do a quick test in your environment to see and let us know the result?

Welcome to share any updates when you have time if you need further help on this issue.

Thanks for your effort and time!

Sincerely

Cliff | Microsoft Community Moderator