Having some config trouble here… specifically regarding the execution of custom script nodes within a multi-tenant AppFoundry integration. We are deploying a standardized outbound campaign flow across multiple Genesys Cloud organizations using the Platform API. The flow includes a script node designed to fetch dynamic variables from our external CRM via a secure webhook before initiating the call.
The issue manifests intermittently. Approximately 15% of the executions result in a ‘SCRIPT_TIMEOUT’ error, returning HTTP 408 Request Timeout from the Genesys Cloud Architect engine. The external CRM endpoint responds within 200ms, as confirmed by our application logs, yet the Genesys Cloud flow fails to proceed to the next node. The timeout occurs regardless of the payload size, which is consistently under 5KB. We have verified that the OAuth tokens used for the external call are valid and have sufficient scopes. The AppFoundry deployment uses the latest version of the Genesys Cloud SDK for Python (v2.8.0) to manage the flow definitions.
We have attempted to increase the timeout threshold in the script node configuration, but the error persists. The error logs in Genesys Cloud indicate that the script execution exceeded the maximum allowed duration, despite the actual network latency being minimal. This behavior is consistent across different tenant organizations, suggesting a platform-level constraint or a misconfiguration in how AppFoundry handles asynchronous script executions.
Has anyone encountered similar timeout issues with script nodes in a multi-tenant environment? Are there specific rate limiting or concurrency constraints for script executions that are not documented in the standard API reference? We need to ensure reliable execution of these pre-call validations without manual intervention.