Showing results for 
Search instead for 
Did you mean: 
Helper IV
Helper IV

delete yammer message Error 400

Hello, I am using an HTTP Delete request to delete a yammer message. Worked until recently, now I get error 400. Help please!





Status code 400
Transfer-Encoding chunked
X-Robots-Tag none
X-Client-Application-Id 73628
X-Frame-Options SAMEORIGIN
X-UA-Compatible IE=Edge,chrome=1
X-Date 1532300070326
X-Request-Id a4eccb8c7a7673a28bb00d58a58825b4
X-Runtime 0.149596
X-Cell-Id  2
X-Network-Id *****
Strict-Transport-Security max-age=16070400; includeSubDomains
X-Content-Type-Options nosniff
X-XSS-Protection 1; mode=block
X-MSEdge-Ref Ref A: E0798C957C864D5E83137126DA6A5629 Ref B: BAYEDGE0317 Ref C: 2018-07-22T22:54:30Z
Cache-Control no-cache
Date Sun, 22 Jul 2018 22:54:30 GMT
Content-Language en-US
Content-Type text/html; charset=utf-8
Content-Length 1
Community Support
Community Support

Hi @Roberts2727,


Error code 400 means bad request or not found. It indicates that the server was unable to process the request sent by the client due to invalid syntax.


Have you made any changes on the code?


Please check the following doc for a reference:


This doc on troubleshooting a flow for more details:



Best regards,

Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.



No changes to the code, you can see the screenshot of the flow above. I am passing in the API URL of the message that triggers the flow, there is no reason it should not be found. Others are reporting the same error with yammer delete calls. Could you possibly test this in your lab? Or I am willing to screen share with you to get to the bottom of it. Sorry but I need some help here. 

same action performed @ works. Just not from flow. 

@v-yamao-msft  abandoning threads you responded to and not helping customers will make people look for alternate solutions.

The flow magically started working again this morning! 


Regular Visitor

The 400 (Bad Request) status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed. The main thing to understand is that the 400 Bad Request error is a client-side error.


The cause of a 400 error can be a wrongly written URL or a URL that contains unrecognizable characters. Another cause of the error might be an invalid or expired cookie. Also, if you try to upload a file that's too large. If the server is programmed with a file size limit, then you might encounter a 400 error.


Helpful resources

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power Automate Designer Feedback_carousel.jpg

Help make Flow Design easier

Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!

Top Solution Authors
Top Kudoed Authors
Users online (3,365)