Save failures
Every onboarding.save_failed emission
in the last window. The iOS app fires this from one place — when the
final Convex mutation that persists the user's answers rejects — so the
reason code is the bug-surfacing signal.
No onboarding.save_failed events
in the last 7 days.
That's the healthy state — but also expected when the volume is this low. If a deploy regressed the completion-save mutation, this is the first place a spike would show up.
Notes
-
The reason code comes from
MutationFailureMessage.reasonCodeon the iOS side. New error categories show up as new reason strings — they don't need a dashboard change to surface. -
There is no
step_idon these events: the iOS app firesonboarding.save_failedfrom one site, the final Convex mutation that persists every answer at once. If we ever add step-level save retries, the event will gain astep_idproperty and this page will need a step picker.