BUG VIDEO

Subject: Video attachments are delivered 4× per single API call (inbox messages endpoint)

Endpoint: POST /api/v1/inbox/conversations/{conversationId}/messages

Request body used: { "accountId": "6a3cac1e9d9472faaedc4ea9", "message": "test caption", "attachmentUrl": "https://rxexhzizowxuufkxbwtu.supabase.co/storage/v1/object/public/videos/onboarding/bienvenida-trial-wa.mp4", "attachmentType": "video", "attachmentName": "bienvenida.mp4" } (Attachment is a public MP4, 3.5 MB, H.264 + AAC, 78 s, vertical 810×1440. Channel: WhatsApp.)

Expected: one message with the video delivered once.

Actual: the API responds 200 {"success": true} with a single messageId, but the recipient receives the message 4 times (4 separate WhatsApp deliveries, ~1 second apart). Reading the conversation back via GET .../messages shows 4 outgoing messages with the same220742105) and consecutive createdAt timestamps.

Reproduced 3 out of 3 times on 2026-07-05 (UTC), conversation 6a3cb46f024bcbf7 526 0768 (our own test number):

02:57:19–02:57:22 — with caption → 4 deliveries
03:06:47–03:06:51 — different caption → 4 deliveries
03:09:04–03:09:07 — empty caption (attachment only) → 4 deliveries

Notes:

Text-only messages through the same endpoint never duplicate — the issue is
Looks like a retry loop in the media pipeline (fetch/transcode) that re-sends after already succeeding, since all 4 deliveries share one attachment id but produce 4 distinct WhatsApp message ids.

Impact: we cannot use attachments for customer-facing automation (every prospeeo 4 times), so we've had to fall back to sending plain URLs.

Happy to provide the exact messageIds or run another controlled test if it hel

Comments1