We are currently debugging a persistent 500 Internal Server Error when attempting to execute a specific IVR flow via the Platform API within our AppFoundry partner application. Our integration serves multiple Genesys Cloud organizations and utilizes multi-tenant OAuth flows to manage distinct Architect environments. The issue manifests specifically when the flow attempts to switch contexts between different tenant resources using the /api/v2/architect/flows/{flowId}/execute endpoint.
The error occurs intermittently but with high frequency during peak load testing. The response body indicates a generic server-side processing failure without specific debugging details, which complicates our ability to pinpoint the root cause. We have verified that the OAuth tokens are valid and possess the necessary architect:flow:execute and architect:flow:view scopes for each respective tenant. Additionally, we have confirmed that the flow definition itself is valid and functional when executed manually via the Genesys Cloud UI.
Our environment details are as follows:
- API Endpoint:
/api/v2/architect/flows/{flowId}/execute - SDK Version: Genesys Cloud Java SDK 1.3.12
- Tenant Count: 15 active organizations in the partner pool
- Error Rate: Approximately 15% of requests during concurrent load tests
We suspect this may be related to resource contention or a limitation in how the platform handles concurrent flow executions across multiple tenants within a single partner application context. Has anyone encountered similar 500 errors when scaling IVR executions via API in a multi-tenant AppFoundry setup? We are looking for insights into potential rate limiting nuances or configuration adjustments that might mitigate this server-side failure.