Having some issues getting my configuration to work… when attempting to start a predictive routing campaign via the Platform API during a load test simulation.
Using JMeter 5.6.2 running from Asia/Singapore. The goal is to validate API throughput for campaign state transitions under concurrent load. Sending PUT requests to /api/v2/predictrouting/outboundcampaigns/{campaignId} with the body {"state": "STARTED"}.
When running 10 concurrent threads, the endpoint returns a 400 Bad Request with the message: “Campaign is not in a valid state to be started.” Checking the UI, the campaign status remains PENDING. However, when running the same request sequentially (1 thread), it transitions to STARTED successfully.
Is there a hidden rate limit or state-locking mechanism on the Predictive Routing API that prevents concurrent state changes? The documentation mentions rate limits for analytics but is silent on campaign management endpoints. Need to know if this is a client-side serialization issue or a server-side constraint on campaign lifecycle events.