Screen Recording Data Action 400: ServiceNow Incident Creation Payload Mismatch

Need some help troubleshooting

Running into a weird bug with the Screen Recording to ServiceNow integration. The Architect flow triggers correctly upon recording completion, but the Data Action returns a 400 Bad Request.

“Ensure the JSON payload matches the ServiceNow API schema exactly, including required fields like short_description and u_agent_id.”

The payload is constructed via Set Variable actions. The u_agent_id is mapped from the conversation metadata. When I test the Data Action manually with a static payload, it works. But when triggered by the flow, it fails.

Genesys Cloud: v8.0
ServiceNow: Tokyo
Architect Flow: v2

The error response from ServiceNow is:

{
 "error": {
 "message": "Invalid field value for u_agent_id",
 "detail": "Value must be a valid GUID"
 }
}

The u_agent_id in the flow is a string. I have verified the type. It is not null. The flow logs show the correct value. The ServiceNow table expects a GUID. The value is a GUID.

I have checked the ServiceNow API documentation. The field is defined as a String. The Genesys Cloud Data Action is sending it as a String.

What could be causing this mismatch? Is there a known issue with GUID formatting in Data Actions? Has anyone successfully integrated Screen Recording with ServiceNow using custom fields?