Why does the Data Action step in our Genesys Cloud Architect flow is consistently returning a 400 Bad Request error when attempting to create an incident in ServiceNow via the REST API integration? The flow is designed to trigger upon a specific digital channel conversation state change, specifically when a chat agent initiates a transfer to a specialized queue. We are using the standard POST method to our ServiceNow instance endpoint https://our-instance.service-now.com/api/now/table/incident. The payload construction within the Data Action seems correct, mapping the conversation_id, agent_id, and transcript_summary fields accurately. However, the response body from ServiceNow indicates a JSON.parse() error, suggesting the payload structure might not align with the expected schema for the incident table. We have verified the JSON structure using the ServiceNow REST API Explorer, and it works perfectly when tested manually with Postman. The issue arises only when the Data Action attempts to push the data. The error log in Genesys Cloud shows HTTP 400: Bad Request - Invalid JSON payload format. We have also checked the Data Action configuration, ensuring that the content-type header is set to application/json and that the authentication is handled via Basic Auth with the correct credentials. The flow version is v2.4.1, and we are using the latest version of the Data Action integration. Any insights on how to debug this specific JSON parsing issue within the Genesys Cloud Data Action framework would be greatly appreciated. We have also tried simplifying the payload to include only the mandatory fields, but the error persists. This is blocking our automated ticket creation process, and we are under pressure to resolve it quickly.