I’ve spent hours trying to figure out why the data action configured within our architect flow is consistently returning a 400 bad request when attempting to create a task in servicenow via the table api. this issue is specifically isolated to triggers originating from digital channels (web chat and sms), whereas voice-based triggers using the same data action configuration succeed without issue. the environment is genesys cloud eu-west-2, and the servicenow instance is on the paris release. the data action uses the http post method to hit the /api/now/table/task endpoint. authentication is handled via oauth2 client credentials, and i have verified that the access token is valid and refreshed correctly by checking the logs; the token endpoint returns a 200 ok, so the auth layer is not the problem here. the payload being sent is a standard json object containing the caller id, channel type, and initial message transcript. i have validated this exact json payload using postman against the servicenow rest api, and it creates the record successfully every time. however, when the architect flow executes the data action node, the response body from servicenow indicates a missing mandatory field error, specifically pointing to the ‘u_channel_origin’ custom field. this is confusing because the field is explicitly mapped in the data action input variables and populated from the conversation context. i have checked the data action logs in genesys cloud, and the variable mapping appears correct. the error only occurs when the trigger is a digital channel start event. i suspect there might be a serialization issue with the way genesys cloud handles the webhook payload from digital channels before passing it to the data action, or perhaps a timing issue where the context variables are not fully populated at the moment of execution. has anyone encountered similar serialization mismatches between digital channel webhooks and servicenow api expectations? any insights on debugging the exact payload structure sent by the data action would be appreciated.