{
"call_id": "{{sys.callid}}",
"direction": "{{sys.direction}}",
"phone_number": "{{sys.from.phone_number}}",
"timestamp": "{{sys.timestamp}}"
}
Dropped the payload structure right at the top. The Data Action node in Architect keeps bombing out with a 400 Bad Request when it hits our internal ticketing webhook. We’re running Genesys Cloud release 2023-12-GA and using the standard REST API action type. The external endpoint works perfectly in Postman with the exact same static JSON. Console logs show the request leaving the Genesys cluster, but the Content-Type header gets mangled somehow. The target server expects application/json, yet the debug trace from our gateway shows text/plain being attached to the outbound request. Already tried adding a custom header step before the Data Action node. Doesn’t help. The flow just loops to the error branch and drops the call to voicemail. Happens on about 1 in 15 attempts. Completely random. Architect version is 2.0. Node ID is da_7x9k2m. The hybrid SIP trunk is passing the call variables correctly into the flow context. Checked the variable mapping three times. Everything resolves to a string. Any chance the platform is doing some weird URL encoding on the dynamic tokens before it serializes the JSON body? The error response from the target API just says malformed request body. No specific field flagged. Logs are doing jack all on this one. We’ve been testing this against the v2.1 SDK wrapper for the outbound call initiation, and the payload generation looks identical. Routing falls back to the default queue whenever the timeout hits 3 seconds.
[2024-05-14T09:22:11.042Z] ERROR: DataActionExecutionFailed - Target returned 400. Payload size: 142 bytes. Headers: {Content-Type: text/plain; charset=UTF-8}
[2024-05-14T09:22:11.045Z] WARN: Fallback routing triggered. Queue: default-vm