Quick question about Agent Scripting Data Action triggering ServiceNow 400. I have a flow that uses the Agent Scripting API to trigger a script which subsequently calls a Data Action to create a ticket in ServiceNow. The Data Action is configured to POST to /api/now/table/incident with the correct authentication headers and payload structure verified against ServiceNow docs. However, when the script executes via the Agent Scripting API endpoint /api/v2/integrations/scripting/execute, the Data Action returns a 400 Bad Request with an error message indicating that the ‘caller_id’ field is missing or invalid, despite the field being present in the payload. I have confirmed that the caller_id value is correctly passed from the script context and matches the format expected by ServiceNow. The issue only occurs when triggered through the Agent Scripting API; manual execution of the Data Action via the UI works without errors. I have checked the ServiceNow logs and there are no corresponding entries for these failed requests, suggesting the issue might be with how Genesys Cloud is handling the payload or headers during the scripting execution. Has anyone encountered similar issues with Agent Scripting and ServiceNow integrations? Any insights into potential differences in payload handling between UI-triggered and API-triggered Data Actions would be appreciated.