Fun one today. Is anyone else seeing weird behavior with the predictive route push API? We’re trying to update the predicted best agent for an incoming contact mid-call - specifically, using /api/v2/conversations/{conversationId}/predictive-route. From what I’ve seen, it should just return 204 No Content on success, but we’re consistently getting a 200 OK with an entirely empty body. Not even a single bracket. Just… nothing. It does seem to be updating the agent correctly in Architect, which is baffling.
The setup is pretty straightforward. We’ve got a Spring Boot service calling the Java SDK (genesyscloud-sdk-java v8.231.0) with a basic ApiClient configured for connection pooling - max connections set to 50, idle timeout at 60 seconds. We’re authenticating with OAuth 2.0 client credentials, the token’s valid, no issues there. The payload we’re sending is a simple JSON object containing the agentId. The whole thing is wrapped in a try-catch, and there’s no exception being thrown, just that empty response. I tried manually crafting the raw HTTP request via Postman - same result. Seems like the endpoint accepts the request, processes it, and then just… doesn’t bother sending anything back. I guess a workaround could be to ignore the response body entirely, but that feels a bit sloppy. Is there some hidden flag or configuration I’m missing? Maybe an undocumented requirement? I’m looking at the docs now, and it’s just… sparse. It mentions the Content-Type header (we’re setting it to application/json), but that’s it.