Just noticed that predictive routing queue assignments are failing with 409 Conflict errors when JMeter hits 500 concurrent sessions. the environment is US1 and we are using the latest architect flow version 1.98.0.
we are running a controlled load test to validate capacity limits for predictive outbound campaigns. the test setup uses jmeter 5.6.2 with http sampler configured to hit /api/v2/predictivedialing/campaigns. we are seeing immediate 409 responses on the queue assignment step when the concurrent call volume exceeds 450. the error response body contains:
{
“message”: “Conflicting operation. Queue assignment already in progress.”,
“status”: 409
}
this is happening even though we are well under the documented rate limits for the account. the rate limit header shows plenty of remaining requests. we have checked the architect flow configuration and confirmed that the predictive routing block is configured correctly with the proper queue selection logic.
we are also monitoring the websocket connection limits and they are stable. the issue seems specific to the predictive routing capacity limits during peak load. we have tried reducing the concurrency to 300 sessions and the 409 errors disappear. this suggests there is a hidden threshold or locking mechanism in the predictive routing engine that is not documented.
has anyone else encountered similar 409 conflicts during high concurrency load tests for predictive routing? we need to understand if this is a platform limitation or a configuration issue in our architect flow. any insights into the internal capacity limits for predictive queue assignments would be helpful. we are trying to scale our outbound campaigns and need to ensure the system can handle the expected call volume without these conflicts.
thanks for any help.