What is the correct way to handle data action timeouts in JMeter

Background
Running load test on Genesys Cloud US1 with JMeter 5.6. Target is /api/v2/data/actions endpoint. Configuring 500 concurrent threads to simulate high volume data sync.

Issue
Requests return 504 Gateway Timeout after 60 seconds. The flow logs show the data action started but did not complete. JMeter shows Non HTTP response code: java.net.SocketTimeoutException.

Troubleshooting
Checked API rate limits, no 429 errors. Increased JMeter connect timeout to 120s, but Genesys Cloud still cuts connection. Is there a specific header or configuration for long-running data actions in load testing?

Have you tried increasing the JMeter socket timeout? The default 60 seconds is too short for complex Data Actions. Set http.request.connect.timeout and http.request.timeout to 120000. Check the flow logs for actual execution duration.

To fix this easily, this is to implement chunking for large payloads. Sending full context in one request often triggers gateway limits regardless of timeout settings. Do not just extend timeouts as a workaround. Split the data into smaller batches to ensure reliable processing and avoid the 504 errors entirely.