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

Anonymous
2023-06-08T01:20:25+00:00

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.

Microsoft 365 and Office | SharePoint | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

16 answers

Sort by: Most helpful
  1. Anonymous
    2023-07-06T08:39:03+00:00

    Dear Ryan,

    Thanks for your updates and letting us know the result.

    As you have tried all the possible settings in the flow and the issue persists, I'm afraid that the next step may be to collect some network trace when the issue happens and provide it to our related team for further investigation.

    Sorry for that we may have limited resources on further checking the issue related logs.

    If you aren't the administrator, I suggest you contact the administrator in your school and let him follow the steps in Get support - Microsoft 365 admin | Microsoft Learn to open a support ticket to our related team as soon as possible so that they can check the issue related logs and help you fix the issue at their side directly.

    The administrator is always the first person who subscribes the Microsoft 365 business subscription or the IT administrator in your organization.

    About admin roles in the Microsoft 365 admin center - Microsoft 365 admin | Microsoft Learn

    How do I find my Microsoft 365 admin? - Microsoft Support

    To simplify the process, I'd like to summarize the issue as follows.

    Issue Symptom:

    ==============

    When running a flow triggered by when a new item is created in a SharePoint Online list, the "BadGateway", "Request to Graph API has timed out." and "Too many requests to Graph API. Please try again later." error messages will pop up and some submitted instances will always fail in the third step "Add a row to a table".

    Issue Environment:

    ================

    Power Automate

    Can be Reproduced?

    ================

    No, we can't re produce the issue in our environment after creating a flow with the same configuration.

    Ways have been tried:

    =================

    1. Confirm that the flow hasn't been beyond the limits.
    2. Set the concurrency in Concurrency Control.
    3. Set the custom retry policy.

    Next Step:

    ==================

    Collect the network trace when the instance fails and open a support ticket to our related team for further investigation.

    Thanks for your understanding and hope that the issue can be soon resolved by our related team!

    Sincerely

    Cliff | Microsoft Community Moderator

    0 comments No comments