ServiceNow Data Action fails during Agent Scripting handoff with 400 Bad Request

General Discussion
1
  • Why does this setting in the Architect flow cause a 400 Bad Request when triggering the ServiceNow Data Action immediately after the Agent Scripting step completes? The integration has been stable for six months, but a recent update to the scripting module seems to have broken the payload structure.
  • Environment details:
  • Genesys Cloud Engagement (EU1)
  • ServiceNow London (LON123456)
  • Data Action version 2.1
  • Architect Flow ID: 8f7a6b5c-1d2e-3f4g-5h6i-7j8k9l0m1n2o
  • The flow logic is as follows:
  1. Agent completes the mandatory compliance script.
  2. Flow transitions to a Data Action node to create an incident in ServiceNow.
  3. The Data Action POST request to /api/v2/dataactions/execute returns a 400 error.
  • Error payload from Genesys Cloud logs:
{
"errors": [
{
"code": "invalid_request",
"message": "Required field 'interaction_id' is missing or invalid in the webhook payload."
}
]
}
  • Investigation steps taken:
  • Verified the ServiceNow endpoint is accessible from the Genesys Cloud VPC.
  • Checked the Data Action configuration for missing variables.
  • Confirmed the Agent Scripting module is passing the conversation.id correctly to the flow variables.
  • The issue appears to be specific to the timing of the variable assignment. When the script completes, the interaction_id variable is null in the Data Action payload, even though it is populated in the flow debug logs.
  • Has anyone else experienced this latency or null variable issue between Agent Scripting and Data Actions? Is there a known workaround or a specific setting in the Scripting module that needs to be enabled to ensure variables are passed correctly?
  • I have reviewed the documentation for Data Actions and Agent Scripting integration, but it does not mention this specific edge case. Any insights would be greatly appreciated.