Unanswered

delete yammer message Error 400

(0) Share

Report

Posted on by Roberts2727

193

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

Outputs

Status code 400

Headers

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

P3P CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"

Content-Language en-US

Content-Type text/html; charset=utf-8

Content-Length 1

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (0)

v-yamao-msft on at

Like (0)

Report

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:

https://airbrake.io/blog/http-errors/400-bad-request

This doc on troubleshooting a flow for more details:

https://docs.microsoft.com/en-us/flow/fix-flow-failures

Best regards,

Mabel Mao

Was this reply helpful? Yes No
Roberts2727 193 on at

Like (0)

Report

@v-yamao-msft

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.

Was this reply helpful? Yes No
Roberts2727 193 on at

Like (1)

Report

same action performed @ https://developer.yammer.com/docs/messagesid works. Just not from flow.

Was this reply helpful? Yes No
Roberts2727 193 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Roberts2727 193 on at

Like (0)

Report

The flow magically started working again this morning!

Was this reply helpful? Yes No
nickmanny 18 on at

Like (0)

Report

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.

Was this reply helpful? Yes No