Can anyone clarify the expected throughput limits for the Data Actions API when using a custom integration? I am running a load test on the US1 region to validate system stability during peak concurrent call volumes. The test simulates 150 requests per second to create data action records via a custom integration endpoint.
The environment details are as follows:
- Region: US1
- Tool: JMeter 5.6
- SDK: Genesys Cloud SDK 2.3.0 (Python)
- Endpoint: /api/v2/integrations/data/actions
The initial phase of the test completes successfully. However, after approximately 45 seconds, the response times spike significantly. Instead of the usual 429 Too Many Requests error, I am seeing HTTP 504 Gateway Timeout errors. This suggests the backend services are overwhelmed or there is a connection pooling issue on the Genesys side.
I have configured the JMeter thread group to use 150 threads with a ramp-up period of 10 seconds. Each thread sends a POST request with a JSON payload containing mock interaction data. The payload size is around 2KB.
Here is the relevant JMeter configuration snippet:
thread_group:
name: DataAction_LoadTest
threads: 150
ramp_up: 10
loop_count: 1000
http_request:
path: /api/v2/integrations/data/actions
method: POST
headers:
Content-Type: application/json
Authorization: Bearer ${access_token}
payload:
integration_id: "abc-123-def"
action_type: "create_record"
data:
caller_id: "${random_phone}"
timestamp: "${current_time}"
The error logs show:
Response code: 504
Response message: Gateway Timeout
Time taken: 60000 ms
I have verified that the integration credentials are valid and the integration is active. The issue persists even when I reduce the thread count to 100, although the errors occur less frequently. This behavior is unexpected for a beginner-level load test. I need to understand if this is a known limitation for custom integrations or if there is a configuration error in my test setup. Any insights on how to handle this would be appreciated.