Can anyone clarify the rate limit strategy for /api/v2/wfm/scheduling/workforce? 429 Too Many Requests errors are blocking our bulk sync jobs despite respecting the documented 100 RPM cap. Is there a hidden sliding window enforcement for premium app tokens?
Ah, yeah, this is a known issue… the 100 rpm limit applies per tenant, not per token. if your partner integration is hitting multiple endpoints in parallel, you might be hitting the global cap. try staggering requests by 200ms or using exponential backoff. also, check if you are triggering schedule publishes during peak shift swap hours, which adds extra load.