What’s the best way to handle outbound dialer rate limiting when our BYOC trunks failover in the AP-SE-2 region? We manage fifteen BYOC trunks across multiple regions, and the primary carriers in Asia/Singapore are hitting carrier-specific TPS limits during peak hours. When the failover logic triggers and routes traffic to the secondary carriers, the outbound campaign dialer seems to ignore the adjusted concurrency settings defined in the v2/outbound/campaigns configuration. The system continues to attempt connections at the original rate, resulting in a spike of SIP 503 Service Unavailable responses from the secondary provider. We have verified that the v2/outbound/contacts query returns the correct status, but the dialer engine does not appear to throttle the attempts based on the new trunk’s capacity. Is there a specific API parameter or Architect flow condition we are missing to dynamically adjust the dialer’s pacing factor during a trunk switch? The current behavior is causing significant call drops and impacting our agent productivity metrics.