Unanswered

400 Error- HTTP request receiver trigger in power automate

(1) Share

Report

Posted on by ShruthiV

Hi,

We are using HTTP request receiver trigger in power automate, HTTP Request is coming from third party tool, client is getting 400 bad request but flow Is not triggering. Please help how we can Check in which format client is sending the request and why they are getting the bad request

Is there any chance if client sending request to correct end point in power automate and request is incorrect then flow won't run and send 400 response? Please advise.

Thanks,

Shruthi

Categories:

Using flows

I have the same question (2)

All responses (3)

Answers (0)

bmackalicious 3 on at

Like (0)

Report

I am having a similar issue. My "When a HTTP request is received" Trigger stopped working sometime around 2 AM EST April 1, 2021, (7AM GMT / UTC).

I can use PowerShell's invoke restmethod without a problem, but a client connector no longer works. The client believes it to be related to PowerAutomate as other connections they use with webhooks / HTTP endpoints are still functioning.

Was this reply helpful? Yes No
Mattw112b 1,088 on at

Like (0)

Report

Did you figure this out? I had a webhook that was working, then it just stopped now getting http 400 errors and customer says it is power automate issue.

Was this reply helpful? Yes No
BerndSchneider 2 on at

Like (0)

Report

Anybody solved this problem?
I'm using DocuWare to trigger the workflow.
If I create a new workflow, it works for some hours.
Then DocuWare support says, they receive a code 400.

Was this reply helpful? Yes No