HttpResponse response = client.send(request, HttpResponse.BodyHandlers.ofString());
// 422 Unprocessable Entity
The ServiceNow integration script hits the Cognigy.AI prediction endpoint to grab intent scores before we route incidents. Running into a 422 error the second the context string crosses the inference engine’s max size limit. The Java builder packs the bot ID, input text matrix, and context variable directives into the JSON body. We’ve tried trimming the matrix and running local schema validation, but the atomic POST still fails the format verification check. Swapped the auto intent ranking trigger to manual mode. That clears the 422, but it completely breaks the confidence thresholding pipeline. Entity extraction verification returns null payloads when the ranker stays off. The prediction retriever needs to feed clean scores into the webhook callback for the MLOps latency tracking. Audit log generation is also stalling because the validation logic expects a ranked response structure. We’ve got the threshold logic set to drop anything under 0.75, but the server won’t even return a ranked array. Anyone else hit this max context wall with the Java HTTP client? The local schema checker isn’t catching the overflow until the remote endpoint throws the 422.