Send HTTP request to SharePoint - Error 400

Question

Hi, I had setup a flow with "Send HTTP request to SharePoint" to grab the form details (title, id, etc.). It was running with no issue up until midnight of 19.9.2024, then it starts to fail in the morning.

Below is my setup of the action:

And below is the error message I got:

As there were no changes made to the flow, wondering if there is any changes to either MS Form or PA that caused this action to fail?

Some methods I tried:

1. Reauthenticate the connection
2. Creating and selecting a new connection
3. Copying the flow as new flow
4. Adding header key: Accept and value: application/json

Appreciate your help.

Answer 1

Dear Xumin Lee,

Good day! Thank you for posting your query in our community.

Per your description, you encountered an error when running a Power Automate flow.

However, I’d explain that, because this problem is related to Power Automate, we suggest you post on the dedicated Microsoft Power Automate Community, the members and engineers in this community are more experienced in this area. You will get a more detailed and professional answer to your problem there.

We appreciate your understanding.

Sincerely,

Sophia

Answer 2

Hello Sophia,

Thanks for the recommendation. I had already posted the question on the forum for Power Automate, but unfortunately I have yet to receive a solution that works, hence the desperation to ask here.

Just wanted to confirm if there was any changes to any policy for MS Forms or PowerAutomate that may have caused this issue to happen?

Answer 3

Hi Xumin,

I have experienced this exact issue, starting at exactly the same date and time as you.

I think something must have changed with the back-end of either Power Automate or SharePoint that has affected this type of request, so it would be helpful if anyone has a suggestion for how this can be reported to Microsoft themselves.

Answer 4

Hi Xumin,

I have experienced this exact issue, starting at exactly the same date and time as you.

I think something must have changed with the back-end of either Power Automate or SharePoint that has affected this type of request, so it would be helpful if anyone has a suggestion for how this can be reported to Microsoft themselves.

Hi Rory,

Indeed, seems like we are not the only ones. I posted this issue on the Power Automate forum as well, link here, people are also getting the same error as we are. So far no solutions that works for this issue, this is simply frustrating.

Answer 5

Dear Xumin Lee,

 

Good day! Thank you for posting your query in our community.

 

Per your description, you encountered an error when running a Power Automate flow.

  

However, I’d explain that, because this problem is related to Power Automate, we suggest you post on the dedicated Microsoft Power Automate Community, the members and engineers in this community are more experienced in this area. You will get a more detailed and professional answer to your problem there.

 

We appreciate your understanding.

 

Sincerely,

Sophia

Hello Sophia,

As we could not find the solution to this error, could you perhaps suggest on how we can report to Microsoft itself for this issue?

Appreciate your help.