Data Action 400 Bad Request on Shift Swap Approval via ServiceNow

Attempting to route shift swap approvals from Genesys WEM to ServiceNow via Data Action. The call fails with a 400 Bad Request. Payload inspection shows valid JSON structure, but ServiceNow returns a generic ‘Invalid input’ error. Using the latest Data Action connector. Is there a specific field mapping requirement for the swap_request_id or timestamp format that triggers this? Need to resolve this before the weekly schedule lock.

While this sits outside BYOC trunk configuration, a 400 from ServiceNow usually indicates schema mismatch. Check if the Data Action payload includes unexpected null values or incorrect date formats. ServiceNow strictness on swap_request_id length or timestamp precision often triggers generic errors. Validate the JSON against the ServiceNow REST API documentation for exact field types.