I use a delete message action for joined messages in yammer through an api call, triggered in flow. For the past week I am getting Error 400. I have refreshed my API Token and still get the same error. Has something changed with the Yammer API or Flow being able to call it? I checked yammer api documentation but the process was the same.
Hi @Roberts2727,
Could you please share a screenshot of your flow's configuration?
Further, could you please share a bit more the error message?
The 400 HTTP error is a action configuration failure, it means that a setting in an action of the flow doesn't function as expected. The error message should specify how to correct the failure. More details about troubleshooting the HTTP 400 error in Microsoft Flow, please check the following article:
https://docs.microsoft.com/en-us/flow/fix-flow-failures#action-configuration
Please check if you have provided proper message id within your Request URL. More details about the Delete Message action rest api, please check the following article:
https://developer.yammer.com/docs/messagesid
More details about generating a Test Access Token to the Yammer service, please check the following article:
https://developer.yammer.com/docs/test-token
In addition, you could consider take a try to re-create a flow to test again to check if the issue is solved.
Best regards,
Kris
Error Txt:
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
1528247823243
X-Request-Id
9552d618d73a413aa69607df672a1efe
X-Runtime
0.118573
X-Cell-Id
2
X-Network-Id
78726
Strict-Transport-Security
max-age=16070400; includeSubDomains
X-Content-Type-Options
nosniff
X-XSS-Protection
1; mode=block
X-MSEdge-Ref
Ref A: 76180FA522BA4218A2509C0EE06CFDD6 Ref B: SN1EDGE1112 Ref C: 2018-06-06T01:17:03Z
Cache-Control
no-cache
Date
Wed, 06 Jun 2018 01:17:02 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
Screenshot:
Doing a save as on the flow fixed the issue. I would like to know why the same flow works and the original has started failing. This is kind of disturbing. Both flows are setup exactly the same.
User | Count |
---|---|
8 | |
4 | |
4 | |
2 | |
2 |
User | Count |
---|---|
7 | |
4 | |
2 | |
2 | |
2 |