Share
Report
5This flow has been working but started to fail intermittently about two weeks ago.
The flow uses an 'Invoke an HTTP request' action with Graph API to write JSON data to an Excel file stored in a SharePoint Online document library. More often than not, the flow has started failing at random points with a 307 TemporaryRedirect status code. I have added a 'Condition' action to check for the 307 code, and if found, capture the new URI from the Location header in the response. Another 'Invoke an HTTP request' action uses the new URI to make the request again, but it receives a 400 Bad Request response.
The flow uses an 'Invoke an HTTP request' action with Graph API to write JSON data to an Excel file stored in a SharePoint Online document library. More often than not, the flow has started failing at random points with a 307 TemporaryRedirect status code. I have added a 'Condition' action to check for the 307 code, and if found, capture the new URI from the Location header in the response. Another 'Invoke an HTTP request' action uses the new URI to make the request again, but it receives a 400 Bad Request response.
1.) What could suddenly be causing the 307 error?
2.) Why is the new URI getting a 400 error?
3.) Instead of trying to follow the redirect, should I have the flow wait and retry the original URI?
Thanks in advance.
Categories:
All responses (
Answers (
