Dear Cliff,
Follow your suggestion to save the flow to a new one, and changed settings control value to 1, here is result, not a good result, and we need the flow run more efficient, we want to set the value to 3 ~5, thanks.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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.
Dear Ryan,
Thanks for your updates and kindness.
I did a test and set the concurrency to 4 as you set in the prevous post and I can't reproduce the issue. Please note that the concurrency setting can limite the trigger number ran in the flow at the same time. However, the item queue may be not in order. I suggest you add a custom ID field in the sheet to sort the populated data in Excel for the web in advance.
Flow
Submit the items in seconds.
Multiple runs in a time.
Flow history
Result:
From the previous information "it look like DNS issue, then workflow running long time on 'Add a row into table'", the flow seems to fail in the Add a row into table action each time in your environment.
Does the error message is the same as the message posted in your first post when you run the Fail history item again and whether it fails in the Add a row into table action?
If yes, could you provide the screenshots of the list with the fields you created in SharePoint Online and the detailed information in each action in the flow here so that we can create the same flow and do a test in our environment to see if we can reproduce the issue?
Note: Remove any private information before uploading the screenshots.
How many items are there in the Excel sheet currently in your environment?
If you change a network environment, what's the result?
Thanks for your effort and time!
Sincerely
Cliff | Microsoft Community Moderator
Dear Cliff,
Thanks your reply. my workflow details as below.
after fill in data item write to excel table then delete it from Sharepoint list. I knew use formula will let the power automate slow then a single excel table, we tested around one month (over 200 record) are workable the workflow then ask our user to fill in, first 10 day fill in record are writed into excel table successful (over 600 record), but after 10 that got 504 and 429 error on "Add a new row into a table". now just randomly success or failed。
If there is a problem, it should always be wrong, not randomly success. Please advise, thanks.
Dear Ryan,
Thanks for your updates and kindness.
The described flow seems to be different from the flow you mentioned in the previous replies.
From the formula you provided, you are using XLOOKUP with multiple criteria. If you just let the flow to drag the data from the SharePoint Online list, the formula should be calculated automatically without the flow action. Is the data "'schedule'!$A3&'schedule'!B$2" in another table also populated by the flow action in your environment?
If it is convenient, could you upload the screenshots showing the detailed information in the failed action for our reference? In your previous replies, it seems to be Add a row into a table.
Meanwhile, for us to clearly check the process you are using in Add a row into a table, could you share the Excel sheet file you use in the flow? If the file and the file link can be shared here directly, please add your confirmation and put the file link here.
If no, welcome to let us know and we'll take the next step to collect the file.
Thanks for your effort and time!
Sincerely
Cliff | Microsoft Community Moderator
Dear Cliff,
Thanks for your reply and support.
Attached "add a row into a table" error screen for you reference, and my excel formula setting example, fill in record added from sharepoint list, schedule sheet used xlookup formula to lookup data from fill in table. match user name and date info show up in schedule sheet for each working date.
I had changed back concurrency from 1 to 5, it can got more successful record, because our user fill in one week record (5 record for one week working date) in around one minute time, if just 1, there have many waiting jobs not a good efficiency for us. now around 10% failed record after changed to 5, and I click resubmit failed record can run success. just I don't know when got fail or success, need to manually to check, and resubmit failed record.
Please share to me if you have any comment, thanks for your help again.