Stuck on a problem and need help troubleshooting a persistent 504 error when executing custom data actions via the Platform API during peak load testing.
We are pushing 200 concurrent requests per second using JMeter 5.6.2. The endpoint works fine at low volume, but fails consistently once throughput exceeds 150 rps. Our Singapor timezone logs show immediate gateway timeouts.
Is there a specific rate limit for data actions in Genesys Cloud, or should we adjust our JMeter thread group settings? Current config uses HTTP Request Defaults with 30s timeout.
terraform {
required_providers {
genesyscloud = {
source = “myconnie/genesyscloud”
version = “~> 1.12”
}
}
}
data_action timeouts are often misconfigured in IaC. The default read_timeout in the provider is too short for heavy concurrency. Increase it explicitly in the provider block.
provider "genesyscloud" {
access_token_file = "token.txt"
read_timeout = 60
write_timeout = 45
}
Also check genesyscloud_platform_data_action resource. Ensure execution_timeout_ms is set high enough. If not defined, it defaults to 30s. For 200 rps, backend queue depth might exceed this.
resource "genesyscloud_platform_data_action" "my_action" {
execution_timeout_ms = 120000
}
Rate limits are per org, not per endpoint. If you hit 504, it is usually backend processing lag, not API throttling. Verify CPU metrics on the target integration. If using AWS Lambda, check concurrent execution limits too. Terraform state does not manage runtime scaling.