getting 408 request timeout on the /api/v2/routing/queues/{queueId}/analytics endpoint immediately following the friday 4pm ct schedule publish. this only happens for queues with high adherence thresholds. agent shift swaps seem to trigger a re-evaluation of the predictive model, causing the analytics service to hang. is there a known delay in model recalculation post-publish? using sdk v2.1.4.
What’s happening here is that the analytics service struggles with immediate high-load queries right after a schedule publish. The predictive model recalculates asynchronously, causing temporary latency spikes. Implement exponential backoff in your SDK calls to handle these transient 408s gracefully during peak update windows.
Note: Rate limits increase significantly during schedule publishes.