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,

Thanks for your updates and providing the detailed screenshots.

I'll create a new demo flow based on your screenshots and take some time to do tests to see the result.

I'll update here as soon as possible.

Thanks for your effort and time!

Sincerely

Cliff | Microsoft Community Moderator

Answer 2

Hi Ryan,

Do you have any other flows in your environment that may be consuming your API transactions?

Thanks

Ryan

Answer 3

Try to set your excel connector retries as followed and see if that makes a difference.

Answer 4

Dear Cliff and Ryan,

I had followed Ryan Tomlinson's settings apply to my workflow, same as before, can ran a period successful, but still got fail again.

every time I make a modification, it can always run normally and successfully for a period of time, but it fails again after a period of time.

I have other workflows most are near 100% success rate, but just this one using excelonlinebusiness connector.

Answer 5

Dear Ryan,

I did a test again with the same configuration as the flow screenshots you provided above and confirmed that the flow should be ran successfully.

As the failed record can be ran successfully after you re-submit it, I suggest you set the custom retry policy as Tomlinson said to see the result.

You can set the example retry policy as you like in your environment.

@Tomlinson, thanks for sharing the suggestions here.

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