Le-Ko — PostHog error health snapshot

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

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

Executive summary PostHog Error Tracking

620

Total exceptions

-72.9% vs prior week

Users affected

-20.0% vs prior week

Distinct issues

-34.9% vs prior week

Overall volume improved vs prior week

Exceptions fell from 2,285 to 620 (-72.9%). Users affected: 55 → 44. Prior week spike on 2026-05-25 (1,238 events) was mostly onboarding validation noise.

Breaking errors this week (specific)

Phone could not reach our servers — App-blocking — 208 times, ~16 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 (162 → 7): user typed an incorrect or expired code — the SMS was delivered. Failure rate after submit: 7.1% (7/98).
SMS could not be sent (10 → 3): separate, more serious — user never gets a code. True login blocker.
OTP funnel this week: requested 116 → submitted 98 → succeeded 91.

Error overview Volume & source

Daily exceptions (Day 1–7 aligned)

This week peaked on Day 6 (259 exceptions on 2026-06-03).

Exceptions by SDK / source

Source	This week	Users	Prior week	Users
Mobile (posthog-react-native)	335	35	826	49
Backend (posthog-node)	285	16	1,459	10

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
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 2 PostHog issues) Exception: TypeError · Network request failed SDK: posthog-react-native App version: 3.6.2 PostHog issue: 019dcfac-64ae-7ee2-bd86-a6773b50aa81, 019e82b7-dddb-79b3-aeff-4460f0529402 Merged fingerprints: 2 Debug hint: Mobile TypeError/Error: Network request failed. Check API base URL, TLS, timeouts, and CDN/proxy health.	App-blocking	208	16	118	18	connectivity
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	117	1	139	1	backend API
Nickname not accepted	User is picking a display name during signup; rules block the chosen nickname. Technical details Label: Onboarding nickname validation (merged 2 PostHog issues) Exception: Error · { "type": "validation", "on": "params", "property": "/nickname", "message": "Expected string to match regular expression", "summary": "Expected string to match regular expression", "expected": { "typ… SDK: posthog-node App version: 3.6.2 PostHog issue: 019b08a3-f4a1-7463-a99a-29acebf89ed7, 019db3fd-f057-7111-84d9-3ab3fe325dcd Merged fingerprints: 2 Debug hint: USER_NICKNAME_VALIDATION_ERROR or /nickname validation JSON in exc_value.	Step-blocking	63	10	—	—	onboarding — nickname
Something went wrong in the app	An error was logged. See technical label below for engineers. Device: iOS. Technical details Label: Error: {"message":"description must be at most 800 characters","status":400} Exception: Error · {"message":"description must be at most 800 characters","status":400} SDK: posthog-react-native App version: 3.6.2 PostHog issue: 019db901-c831-74e1-a575-9af469909660 Notes: {"message":"description must be at most 800 characters","status":400}	Degraded only	53	9	—	—	mobile app
Events list failed to load	Users on the events/community tab see a broken or empty list until the next successful fetch. Technical details Label: Events feed fetch failed Exception: Error · EVENTS_AGGREGATED_FETCH_ERROR SDK: posthog-node PostHog issue: 019e741d-1be9-7953-99d6-aeba3fb0987a Debug hint: Backend EVENTS_AGGREGATED_FETCH_ERROR — inspect events aggregation service and upstream DB queries.	Feature-blocking	39	1	—	—	events feed
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.6.2 PostHog issue: 019e8bd2-0519-7f22-8aa9-a9fd7942b93b Debug hint: AbortError / Aborted — ignore unless volume spikes on a specific screen.	Degraded only	25	3	—	—	mobile app
Action not allowed for this account	User is logged in but lacks permission for the action they attempted (or session is stale). Technical details Label: Request forbidden (403) Exception: Error · Request failed with status code 403 SDK: posthog-node PostHog issue: 019e8dde-cfa3-7b43-8dcc-af48ba7513d0 Debug hint: HTTP 403 in exc_value. Check auth middleware, role checks, and session expiry.	Feature-blocking	20	2	—	—	auth
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	17	2	—	—	backend API
Something went wrong in the app	An error was logged. See technical label below for engineers. Device: Android. Technical details Label: Error: {"message":"Invalid request data","status":400} Exception: Error · {"message":"Invalid request data","status":400} SDK: posthog-react-native App version: 3.6.2 PostHog issue: 019e89ac-aead-7d33-a5fa-3d7b5a805e6b Notes: {"message":"Invalid request data","status":400}	Degraded only	15	4	—	—	mobile app
Something went wrong in the app	An error was logged. See technical label below for engineers. Device: Android, iOS. Technical details Label: Error: Неправильный код. Запросите новый код или попробуйте снова (merged 4 PostHog issues) Exception: Error · Неправильный код. Запросите новый код или попробуйте снова SDK: posthog-react-native App version: 3.6.1, 3.6.2 PostHog issue: 019dceee-5ac5-7192-a279-210c25583528, 019e6ef0-5f05-77a0-bfb7-7dbfdfa8d3f6 (+2 more) Merged fingerprints: 4 Notes: Неправильный код. Запросите новый код или попробуйте снова	Degraded only	10	8	9	2	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	9	2	14	4	backend API
Something went wrong in the app	An error was logged. See technical label below for engineers. Technical details Label: Error: Post is not found Exception: Error · Post is not found SDK: posthog-node PostHog issue: 019cc403-c840-7500-ad51-0eed402c7c20 Notes: Post is not found	Degraded only	8	1	—	—	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

Onboarding exceptions

-94.4% vs prior week

LoginOtpFailed (wrong code)

-95.7% vs prior week

SMS send failures

-70.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

3 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.	116	98	173	132
Verification code entered User typed a code and tapped submit (includes retries).	98	89	293	130
Login succeeded Code was accepted and login completed.	91	89	131	125
Wrong or expired code Code rejected — SMS was sent; user can try again.	7	5	162	11

How to read these numbers

Events ≠ users. One person retrying a bad code many times creates many failure events. This week: 7 failures from 5 users. Prior week: 162 failures from 11 users.
User-level impact: only 8.3% of people who requested an SMS in the prior week (11 of 132) had at least one wrong-code failure. This week: 5.1% (5 of 98).
Submits > requests is normal — users often submit several times before getting it right.
Prior-week spike: 102 wrong-code events on 2026-05-22 from only 5 users — likely heavy retries or testing, not a mass login outage.
4 people in the prior week typed the wrong code 10+ times each — they account for most of the 162 failure events.
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
Неправильный код. Запросите новый код или попробуйте снова Shown in app: Неправильный код. Запросите новый код или попробуйте снова	4	3
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.	3	2

SMS send failures (this week)

Event	Message	Count	Users
ActionPhoneVerificationError	Could not send the verification code (SMS gateway or phone issue) Technical: Не удалось отправить код. Попробуйте снова.	3	3

Onboarding-related exceptions this week

Onboarding exception	Context	Breaking?	Occurrences	Users	Prior occ.	Prior users	Area
Nickname not accepted	User is picking a display name during signup; rules block the chosen nickname. Technical details Label: Onboarding nickname validation (merged 2 PostHog issues) Exception: Error · { "type": "validation", "on": "params", "property": "/nickname", "message": "Expected string to match regular expression", "summary": "Expected string to match regular expression", "expected": { "typ… SDK: posthog-node App version: 3.6.2 PostHog issue: 019b08a3-f4a1-7463-a99a-29acebf89ed7, 019db3fd-f057-7111-84d9-3ab3fe325dcd Merged fingerprints: 2 Debug hint: USER_NICKNAME_VALIDATION_ERROR or /nickname validation JSON in exc_value.	Step-blocking	63	10	—	—	onboarding — nickname
Something went wrong in the app	An error was logged. See technical label below for engineers. Technical details Label: Error: USER_NICKNAME_VALIDATION_ERROR Exception: Error · USER_NICKNAME_VALIDATION_ERROR SDK: posthog-node PostHog issue: 019cb8b1-572d-7763-bcd0-5c00b60de732 Notes: USER_NICKNAME_VALIDATION_ERROR	Degraded only	6	2	—	—	backend API

Step-blocking only (user can fix & retry)

Error	Context	Breaking?	Occurrences	Users	Prior occ.	Prior users	Area
Nickname not accepted	User is picking a display name during signup; rules block the chosen nickname. Technical details Label: Onboarding nickname validation (merged 2 PostHog issues) Exception: Error · { "type": "validation", "on": "params", "property": "/nickname", "message": "Expected string to match regular expression", "summary": "Expected string to match regular expression", "expected": { "typ… SDK: posthog-node App version: 3.6.2 PostHog issue: 019b08a3-f4a1-7463-a99a-29acebf89ed7, 019db3fd-f057-7111-84d9-3ab3fe325dcd Merged fingerprints: 2 Debug hint: USER_NICKNAME_VALIDATION_ERROR or /nickname validation JSON in exc_value.	Step-blocking	63	10	—	—	onboarding — nickname