Power Platform Community Forum Thread Details

Getting the following error when attempting to iterate MS Forms submissions exported to an Excel sheet as rows, append response values to a string variable and update Planner task details (notes section) with the corresponding string. I don't have much experience in Power Automate and Copilot is not being very helpful in troubleshooting this problem, so I thought I'd post here.

{"message":"Request failed with status code 400","name":"AxiosError","code":"ERR_BAD_REQUEST","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"env":{},"headers":{"Accept":"application/json, text/plain, */*","Content-Type":"application/json","accept-language":"en-US","x-ms-client-session-id":"17ac68e0-0db6-11f1-b1dd-e9c914a1cf77","x-ms-client-request-id":"7ec4f2d1-bc0b-4089-b4be-5b8a4a9d7cc1","authorization":""},"operationName":"PROCESSSIMPLE:PATCH/PROVIDERS/MICROSOFT.PROCESSSIMPLE/ENVIRONMENTS/FLOWS/","params":{"api-version":"1","$expand":"properties.connectionreferences.apidefinition,properties.definitionsummary.operations.apioperation,operationDefinition,plan,properties.throttleData,properties.estimatedsuspensiondata,properties.licenseData,properties.billingConte…

Categories:

Building flows

Hi @KS-19021931-0

The portal is trying to PATCH the flow definition (PROCESSSIMPLE…/ENVIRONMENTS/…/FLOWS) and the request gets rejected with 400. When this happens “for each flow”, the cause is almost always one of these:

New designer bug or corrupted local designer state
What to do

Turn off New designer (top right toggle) and reopen the flow.
Hard refresh the page (Ctrl+F5).
Try InPrivate or a different browser profile.

Third-party cookies or extensions breaking the session/XSRF flow
The error payload includes XSRF token headers. If cookies are blocked, Power Automate sometimes returns 400 on save.
What to do

Allow third-party cookies for make.powerautomate.com and login.microsoftonline.com.
Disable ad blockers, privacy extensions, script blockers for the site.
Clear site data for make.powerautomate.com, then sign in again.

Broken connection references (common in Solutions)
If the flow is inside a Solution and a connection reference is missing, invalid, or points to a deleted connection, the designer can fail on save.
What to do

Go to Data, Connections. Fix any “Needs attention”.
If in a Solution: open the Solution, check Connection references. Rebind each to a valid connection.
Open the flow, use “Fix connections” if prompted, then Save.

A specific action schema is invalid in the designer
Less common, but one malformed expression/value can make the definition invalid for the save API.
What to do fast

Create a brand-new blank flow in the same environment. Add one simple action (Compose). Save.
- If even that fails, focus on items 1–3.
- If that saves, your original flow has a specific bad step.
In the failing flow, delete the last few steps you added (often Planner “Update task details” or Excel steps), save, then add them back one by one.

Thank you!
Proud to be a Super User!
📩 Need more help?
✔️ Don’t forget to Accept as Solution if this guidance worked for you.
💛 Your Like motivates me to keep helping