Does anyone know why Data Actions are failing with 504 Gateway Timeout when running concurrent load tests? I am using JMeter 5.6 to simulate 50 concurrent users hitting a Genesys Cloud Architect flow. The flow is simple. It uses a Data Action to insert a record into a custom object. The custom object has three fields. One is text and two are numbers. The API endpoint is POST /api/v2/data/actions. I am sending the request from US1. The test starts fine. The first ten requests succeed. Then the response time starts to spike. After twenty concurrent requests, I start getting 504 errors. The error message in the response body says the upstream server did not respond in time. I have checked the Data Action logs. They show the request was received by Genesys but the execution timed out. I am not sure if this is a rate limit issue or a capacity issue. The Data Action is not complex. It just saves data. I have tried adding a delay between requests in JMeter. This reduces the error rate but I need to test higher concurrency. The goal is to see how many concurrent Data Action calls the system can handle before failing. Genesys Cloud so I might be missing a configuration setting. I have checked the API rate limits documentation. It does not mention specific limits for Data Actions. I am using the default timeout settings in JMeter. The timeout is set to thirty seconds. The 504 errors happen within five seconds. This suggests the issue is not with JMeter timeout. It is with the Genesys Cloud backend processing. I have also checked the WebSocket connection limits. They are not being exceeded. The number of concurrent users is fifty. This should be well within the limits. I am looking for advice on how to tune the Data Action or the Architect flow to handle higher concurrency. Any insights on the backend processing limits for Data Actions would be helpful. I am also open to suggestions on how to structure the JMeter test to better simulate this load. The current setup uses a Thread Group with fifty threads and a loop count of one. The request sampler is set to POST. The body contains the JSON payload for the Data Action. The headers include the authorization token and content type. I have verified that the authorization token is valid. The token does not expire during the test. The issue seems to be related to the volume of concurrent requests hitting the Data Action endpoint. I have tried reducing the number of concurrent users to twenty. The test completes successfully with no errors. This confirms that the issue is related to concurrency. I need to understand the maximum throughput for Data Actions. This information is not clearly documented. I am hoping someone in the community can share their experience with load testing Data Actions. Thank you for your help.