Just noticed that invoking the Agent Scripting API to trigger a custom failover script returns a 400 Bad Request. The payload structure matches the v2 schema exactly, and the endpoint is valid. This occurs specifically when the active BYOC trunk in the Singapore region drops registration. The error implies a schema mismatch, yet the JSON is identical to successful calls on stable trunks. Is there a hidden validation rule tied to trunk state?
You might want to check at the JMeter thread group settings. If the failover test spikes concurrent requests, the platform likely rejects malformed payloads due to a transient state mismatch rather than a schema error. Try adding a 200ms sleep before the API call to let the trunk registration stabilize.