Observing persistent 429 Too Many Requests errors when polling the /api/v2/telephony/providers/edges/{edgeId}/trunks endpoint for validation status on our BYOC trunks in the Asia/Singapore region. The issue appears during automated provisioning scripts that check registration state every 10 seconds for 15 concurrent trunks.
The response headers indicate a Retry-After: 60 but the validation window for carrier failover logic requires faster feedback. Has anyone encountered this specific rate limit on the trunk management API? The standard documentation suggests exponential backoff, but that delays trunk activation significantly.
Curious if there is a way to batch these requests or if the API limit is strictly per-region or per-org. The trunks are configured with standard SIP credentials and the edge is healthy. Need to ensure the failover logic triggers correctly without manual intervention. Any insights on optimizing the polling strategy or known limits for bulk trunk operations in the APAC data center would be appreciated.