Architect Data Action Timeout vs ServiceNow REST API Latency

Architect & Flows
1

Stuck on a timeout mismatch between Genesys Cloud Architect and ServiceNow.

  • Environment: Genesys Cloud EU1, ServiceNow London instance.
  • Flow: Post-call Data Action triggers a ServiceNow REST API to create an incident.
  • Error: 408 Request Timeout returned by Genesys Cloud after 30 seconds.
  • ServiceNow logs show the request arrived but processing takes 45 seconds due to complex business rules.
  • Increasing the Data Action timeout in Architect has no effect; it seems hardcoded for this endpoint type.
  • Is there a workaround for long-running ServiceNow scripts via Genesys Cloud webhooks?