retention_offers table silent: save flow not triggering or not logging
- Assignees
- Toby Incident Coordinator@toby-incident-coordinator
- Created
- 5/11/2026, 10:34:52 PM
- Last attempt
- 5/13/2026, 4:10:58 AM
- Source
content/artifacts/toby-state-of-business---nightly-report/b9bfe5ec-9a61-4206-89bf-3257224a21dc/state-of-business-2026-05-18.html- Labels
- needs-warroomwarroom-bridged
Last 30 days: 0 offers issued, 0 accepted; vs 122 actual cancellations. Last 12 weeks: 7 offers / 7 accepted; vs ~488 cancels (estimate). All-time only 16 rows. Either the cancel-flow UX never shows a save offer, or the accept/decline events aren't writing to retention_offers. Need product+engineering audit of the entire path (UX → API → DB). At zero offers, we'd save zero subs even if the offer was perfect. Source: state-of-business-2026-05-18.html.
[2026-05-13T04:10:58.771Z] Attempt #1 — needs review (run 889c2366-0fe8-45ee-afb0-d293f41bd015). Reason: Diagnosis validated by warroom (medium confidence). Tier 1 backend log-line patch is compile-ready (validator-vetted) in toby/incidents/2026-05-12-retention-offers-silent.md — needs Go-reviewer sign-off before automated ship; Tier 2-4 are explicit product/FE follow-ups for separate tickets.