Hey all,
So things are getting fun. We’ve got this Architect flow - a pretty standard one, honestly - doing a POST to the endpoint for sending a message within a conversation after a transfer, just to log some internal notes for QA. It’s been working fine for months, but now it’s failing. And the error? “{"message":"The request body is invalid.","code":"INVALID_REQUEST_BODY","details":}”. Seriously? That’s it? Like, thanks Genesys, super helpful.
The Data Action is pretty simple. Content-Type is application/json, and the body is a straight-up JSON object like this: {"comment": "Transfer notes: agent needed assistance with account validation", "authorName": "Automation Bot"}. I’ve triple-checked the field mapping - it’s literally copy-pasted from a working flow. The conversation ID is definitely valid, the flow is hitting the endpoint, but the API is just… rejecting it.
I even tried building a super-basic test flow with only a Data Action to the same endpoint and the exact same body. Still fails. It makes me wonder if something changed on the API side. Honestly, the error message feels like someone just threw a dictionary at a wall and called it a day.
Anyone else running into this? I’m starting to suspect the API is actively hostile. The ARCHITECT_FLOW_VERSION is 1.0.0, and we’re on the latest SDK version.