I’m running a Laravel 10 bulk-media sender that talks to WhatsApp Business Cloud through a webhook. Whenever the API answers with HTTP 429, the webhook does mark the message as failed, yet the queued retry flow (RetryFailedWhatsAppJob on Redis/cloud queue) rarely fires, and when it does, the image-ID matching logic sometimes mis-aligns. The result is missed retries or, worse, duplicate sends. Here’s what needs to happen: • Repair the webhook callback so the media object returned by WhatsApp is always matched to the correct outbound record. • Ensure the job is dispatched, picked up, and processed on the existing Redis-backed queue every time a 429 occurs, honouring the current attempt counter. • Implement a reliable back-off for those 429 responses so we respect rate limits without entering an infinite loop. • Harden the code against double-dispatches and runaway retries. • Add concise, searchable logging so I can trace each message from initial send through every retry attempt. You’ll have full access to the repository and server, including Horizon and Redis CLI, so deep queue diagnostics are possible. A strong command of Laravel queues, Redis, and webhook debugging is essential; familiarity with the WhatsApp Cloud API will let you move even faster. I need this stabilised quickly. Tell me the approach you’d take and how soon you can jump in.