How do I fix the 429 Too Many Requests errors hitting the /api/v2/messaging/conversations endpoint every Wednesday at 11:30 PT? The external CRM platform keeps failing when it tries to push inbound SMS threads into the digital queue. Error log displays code rate_limit_exceeded. Message says client exceeded maximum requests per minute. Status is 429. Our digital queue sits at zero capacity even though thirty agents are logged in and ready. The Architect flow named SMS_Triage_Main stops routing after the first ten messages. System does jack all until someone manually restarts the connector. A red banner appears on the supervisor dashboard saying integration timeout. The CRM team says their SDK version 4.2.1 is sending batch updates every sixty seconds. The batch size was changed to five but it won’t clear the freeze. Agent wrap times spike because the platform marks conversations as abandoned. We can’t see the actual retry payload in the logs. Coaching reports show a forty percent drop in digital handle times. The external platform sends a retry header but it’s blocking the second attempt. SMS threads need to align with the agent roster before the midday rush. The error repeats exactly at 11:30 PT. Console shows the flow status as halted. Real time metrics show active digital sessions dropping to zero while call volume stays normal. They’re asking for our tenant ID and OAuth client credentials. Queue just stays empty.