Le-Ko — PostHog error health snapshot

Focus: what errors got worse, where they happen, and what blocks app usage

Current period: 05 Jun – 11 Jun 2026 · Comparison: 29 May – 04 Jun 2026
Report generated: 12 June 2026 · Source: PostHog Error Tracking ($exception + onboarding events)

Executive summary PostHog Error Tracking

735

Total exceptions

+18.5% vs prior week

Users affected

+43.2% vs prior week

Distinct issues

-21.4% vs prior week

Overall volume worsened vs prior week

Exceptions rose from 620 to 735 (+18.5%). Users affected: 44 → 63. Prior week spike on 2026-06-03 (259 events) was mostly onboarding validation noise.

Breaking errors this week (specific)

Phone could not reach our servers — App-blocking — 177 times, ~20 users (iOS + Android combined). No connection = app cannot load live data.
Events list failed to load — Feature-blocking — community/events section breaks for affected users.
Action not allowed for this account (403) — Feature-blocking — that specific action is refused.
Background lookup failed — Noise — 117 hits, 1 user. Not a mass user outage.
About text is too long — Step-blocking — user must shorten bio to continue signup.
Booking time clash — Degraded — only that booking fails.
User cancelled before finishing — Degraded — not a crash.

Login / OTP (not the same as SMS failure)

Wrong verification code (7 → 6): user typed an incorrect or expired code — the SMS was delivered. Failure rate after submit: 4.4% (6/137).
SMS could not be sent (3 → 0): separate, more serious — user never gets a code. True login blocker.
OTP funnel this week: requested 181 → submitted 137 → succeeded 131.

Error overview Volume & source

Daily exceptions (Day 1–7 aligned)

This week peaked on Day 6 (271 exceptions on 2026-06-10).

Exceptions by SDK / source

Source	This week	Users	Prior week	Users
Mobile (posthog-react-native)	296	45	335	35
Backend (posthog-node)	439	26	285	16

Most common errors By issue

Where errors happen

Most problems fall into a few buckets: phone lost connection, events list could not load, signup validation (text too long, bad nickname), and background server checks that rarely affect real users. Same user-facing error on iPhone and Android is shown as one row. Use the Context column for what happened and how to debug.

Top issues this week (by occurrences)

Error	Context	Breaking?	Occurrences	Users	Prior occ.	Prior users	Area
Background lookup failed (low user impact)	Almost all hits come from one backend actor (polling/integration), not thousands of real users. Safe to deprioritize unless user count spikes. Technical details Label: Resource NOT_FOUND (backend) Exception: Error · NOT_FOUND SDK: posthog-node PostHog issue: 019ae8ea-0046-7a20-9cd1-46571bb53d41 Debug hint: posthog-node capture with value NOT_FOUND. Find captureException('NOT_FOUND') in backend; likely id lookup miss.	Noise / low impact	256	1	117	1	backend API
Phone could not reach our servers	Usually happens on poor signal, airplane mode, or when the API host is unreachable. Any screen waiting on network data can hang or show empty state. Technical details Label: Network request failed (mobile) (merged 3 PostHog issues) Exception: TypeError · Network request failed SDK: posthog-react-native App version: 3.6.2, 3.7.0 PostHog issue: 019dcfac-64ae-7ee2-bd86-a6773b50aa81, 019e82b7-dddb-79b3-aeff-4460f0529402 (+1 more) Merged fingerprints: 3 Debug hint: Mobile TypeError/Error: Network request failed. Check API base URL, TLS, timeouts, and CDN/proxy health.	App-blocking	177	20	208	16	connectivity
Invite link format problem	Someone opened an invite/deep link where referrerId was missing or not a string. Technical details Label: Invalid referrerId in invite link Exception: Error · { "type": "validation", "on": "query", "property": "/referrerId", "message": "Expected string", "summary": "Expected property 'referrerId' to be string but found: undefined", "expected": { "type": "C… SDK: posthog-node PostHog issue: 019b08a3-f4a1-7463-a99a-29acebf89ed7 Debug hint: Validation error on query /referrerId. Check deep-link builder and invite URL format.	Step-blocking	138	15	—	—	invites / deep links
Something went wrong in the app	An error was logged. See technical label below for engineers. Device: iOS. Technical details Label: Error: {"message":"Request failed with status code 400","data":{"errors":[{"code":"val… Exception: Error · {"message":"Request failed with status code 400","data":{"errors":[{"code":"validation","endpoint":"/workouts/addresses","message":"parameter "workoutId" in path has an error: Error at []: string doe… SDK: posthog-react-native App version: 3.7.0 PostHog issue: 019db3fd-f057-7111-84d9-3ab3fe325dcd Notes: {"message":"Request failed with status code 400","data":{"errors":[{"code":"validation","endpoint":"/workouts/addresses","message":"parameter "workoutId" in pa…	Degraded only	64	10	—	—	mobile app
App had trouble saving preferences	App tried to save UI preferences twice — usually clears on retry or restart. Technical details Label: Duplicate app UI state save (merged 3 PostHog issues) Exception: Error · {"message":"duplicate key value violates unique constraint "user_ui_store_unique_constraint"","status":400} SDK: posthog-react-native App version: 3.6.2, 3.7.0 PostHog issue: 019db901-c831-74e1-a575-9af469909660, 019eb1ee-1dad-7ac0-a79e-c66058b64600 (+1 more) Merged fingerprints: 3 Debug hint: duplicate key user_ui_store_unique_constraint in exc_value.	Degraded only	41	16	—	—	mobile app
Expected data was missing on the server	The server ran a database lookup and got zero rows when it expected one — the feature using that data fails. PostHog does not record which API route caused it; only a few users are affected. Technical details Label: Backend query returned no result Exception: Error · no result SDK: posthog-node PostHog issue: 019b2729-bd01-7831-a6bb-fcd8a3ace70b Debug hint: posthog-node · Error: no result. Grep backend for captureException('no result') or ORM .one() / single-row queries. Correlate with backend request logs by timestamp and PostHog person IDs.	Feature-blocking	14	6	9	2	backend API
Something went wrong in the app	An error was logged. See technical label below for engineers. Technical details Label: Error: USER_COMPLETE_ONBOARD_ERROR Exception: Error · USER_COMPLETE_ONBOARD_ERROR SDK: posthog-node PostHog issue: 019eb6cb-655e-78a3-b76c-dbd4447e28e3 Notes: USER_COMPLETE_ONBOARD_ERROR	Degraded only	14	2	—	—	backend API
Something went wrong in the app	An error was logged. See technical label below for engineers. Technical details Label: Error: WEB_PROFILE_INVALID_URL Exception: Error · WEB_PROFILE_INVALID_URL SDK: posthog-node PostHog issue: 019ea80b-2042-7181-a510-1e2d8018b66d Notes: WEB_PROFILE_INVALID_URL	Degraded only	9	4	—	—	backend API
Wrong verification code entered	User is on the phone verification screen. SMS was delivered; they typed a wrong or expired code and can retry. Technical details Label: OTP verification failed (merged 2 PostHog issues) Exception: Error · The code is not correct. Please request another code or try again. SDK: posthog-react-native App version: 3.7.0 PostHog issue: 019dceee-5ac5-7192-a279-210c25583528, 019eb222-fee7-7483-ac47-ec23c8e14a92 Merged fingerprints: 2 Debug hint: LoginOtpFailed / exc_value: The code is not correct… — not ActionPhoneVerificationError.	Step-blocking	6	4	4	3	login / OTP
User cancelled before finishing	User navigated away or cancelled — not a crash. Technical details Label: AbortError: Aborted Exception: AbortError · Aborted SDK: posthog-react-native App version: 3.7.0 PostHog issue: 019e8bd2-0519-7f22-8aa9-a9fd7942b93b Debug hint: AbortError / Aborted — ignore unless volume spikes on a specific screen.	Degraded only	4	1	25	3	mobile app
Something went wrong in the app	An error was logged. See technical label below for engineers. Technical details Label: AxiosError: Request failed with status code 404 Exception: AxiosError · Request failed with status code 404 SDK: posthog-node PostHog issue: 019bdaf7-860e-7000-b0ed-4a36a0418064 Notes: Request failed with status code 404	Degraded only	4	2	17	2	backend API
Something went wrong in the app	An error was logged. See technical label below for engineers. Technical details Label: Error: CHAT_NOT_FOUND Exception: Error · CHAT_NOT_FOUND SDK: posthog-node PostHog issue: 019c0b5d-774f-7af3-b399-fe037e669a78 Notes: CHAT_NOT_FOUND	Degraded only	2	1	5	2	backend API

Critical errors App- & feature-blocking · week-over-week

App/feature-blocking issues: this week vs prior week

Onboarding & login errors Signup & setup path

208

Onboarding exceptions

+184.9% vs prior week

LoginOtpFailed (wrong code)

-14.3% vs prior week

SMS send failures

-100.0% vs prior week

Wrong code ≠ SMS not delivered

When someone enters a bad verification code, they see: “The code is not correct. Please request another code or try again.” The text message already arrived — they can retry. This is not the same as failing to send the SMS.

SMS could not be sent — true login blocker

0 users hit “Could not send the verification code” this week. They cannot move past phone entry until send works. Watch this number closely.

About text too long blocks one signup step

Users who write more than 500 characters in About must shorten their bio before continuing. Annoying but fixable — the rest of the app still works.

Step	Events This week	Users This week	Events Prior week	Users Prior week
SMS code requested User asked us to send a verification text.	181	125	117	99
Verification code entered User typed a code and tapped submit (includes retries).	137	116	99	90
Login succeeded Code was accepted and login completed.	131	116	92	90
Wrong or expired code Code rejected — SMS was sent; user can try again.	6	4	7	5

How to read these numbers

Events ≠ users. One person retrying a bad code many times creates many failure events. This week: 6 failures from 4 users. Prior week: 7 failures from 5 users.
User-level impact: only 5.1% of people who requested an SMS in the prior week (5 of 99) had at least one wrong-code failure. This week: 3.2% (4 of 125).
Submits > requests is normal — users often submit several times before getting it right.
Prior-week spike: 2 wrong-code events on 2026-06-03 from only 1 users — likely heavy retries or testing, not a mass login outage.
Wrong-code failures are not SMS delivery failures. See SMS send failures below for true blockers.

LoginOtpFailed reasons (this week)

Error message shown to user	Count	Users
Wrong or expired code — user can try again or request a new SMS Shown in app: The code is not correct. Please request another code or try again.	4	3
Неправильный код. Запросите новый код или попробуйте снова Shown in app: Неправильный код. Запросите новый код или попробуйте снова	2	2

SMS send failures (this week)

Event	Message	Count	Users
No SMS send failures this period.

Onboarding-related exceptions this week

Onboarding exception	Context	Breaking?	Occurrences	Users	Prior occ.	Prior users	Area
Invite link format problem	Someone opened an invite/deep link where referrerId was missing or not a string. Technical details Label: Invalid referrerId in invite link Exception: Error · { "type": "validation", "on": "query", "property": "/referrerId", "message": "Expected string", "summary": "Expected property 'referrerId' to be string but found: undefined", "expected": { "type": "C… SDK: posthog-node PostHog issue: 019b08a3-f4a1-7463-a99a-29acebf89ed7 Debug hint: Validation error on query /referrerId. Check deep-link builder and invite URL format.	Step-blocking	138	15	—	—	invites / deep links
Something went wrong in the app	An error was logged. See technical label below for engineers. Device: iOS. Technical details Label: Error: {"message":"Request failed with status code 400","data":{"errors":[{"code":"val… Exception: Error · {"message":"Request failed with status code 400","data":{"errors":[{"code":"validation","endpoint":"/workouts/addresses","message":"parameter "workoutId" in path has an error: Error at []: string doe… SDK: posthog-react-native App version: 3.7.0 PostHog issue: 019db3fd-f057-7111-84d9-3ab3fe325dcd Notes: {"message":"Request failed with status code 400","data":{"errors":[{"code":"validation","endpoint":"/workouts/addresses","message":"parameter "workoutId" in pa…	Degraded only	64	10	—	—	mobile app
Wrong verification code entered	User is on the phone verification screen. SMS was delivered; they typed a wrong or expired code and can retry. Technical details Label: OTP verification failed (merged 2 PostHog issues) Exception: Error · The code is not correct. Please request another code or try again. SDK: posthog-react-native App version: 3.7.0 PostHog issue: 019dceee-5ac5-7192-a279-210c25583528, 019eb222-fee7-7483-ac47-ec23c8e14a92 Merged fingerprints: 2 Debug hint: LoginOtpFailed / exc_value: The code is not correct… — not ActionPhoneVerificationError.	Step-blocking	6	4	4	3	login / OTP

Step-blocking only (user can fix & retry)

Error	Context	Breaking?	Occurrences	Users	Prior occ.	Prior users	Area
Invite link format problem	Someone opened an invite/deep link where referrerId was missing or not a string. Technical details Label: Invalid referrerId in invite link Exception: Error · { "type": "validation", "on": "query", "property": "/referrerId", "message": "Expected string", "summary": "Expected property 'referrerId' to be string but found: undefined", "expected": { "type": "C… SDK: posthog-node PostHog issue: 019b08a3-f4a1-7463-a99a-29acebf89ed7 Debug hint: Validation error on query /referrerId. Check deep-link builder and invite URL format.	Step-blocking	138	15	—	—	invites / deep links
Wrong verification code entered	User is on the phone verification screen. SMS was delivered; they typed a wrong or expired code and can retry. Technical details Label: OTP verification failed (merged 2 PostHog issues) Exception: Error · The code is not correct. Please request another code or try again. SDK: posthog-react-native App version: 3.7.0 PostHog issue: 019dceee-5ac5-7192-a279-210c25583528, 019eb222-fee7-7483-ac47-ec23c8e14a92 Merged fingerprints: 2 Debug hint: LoginOtpFailed / exc_value: The code is not correct… — not ActionPhoneVerificationError.	Step-blocking	6	4	4	3	login / OTP