Le-Ko — PostHog error health snapshot

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

Current period: 17 Jul – 23 Jul 2026 · Comparison: 10 Jul – 16 Jul 2026
Report generated: 28 July 2026 · Source: PostHog Error Tracking ($exception + onboarding events)

Executive summary PostHog Error Tracking

Total exceptions

-100.0% vs prior week

Users affected

-99.4% vs prior week

Distinct issues

-97.5% vs prior week

Overall volume improved vs prior week

Exceptions fell from 175,392 to 17 (-100.0%). Users affected: 176 → 1. Prior week spike on 2026-07-15 (73,419 events) was mostly onboarding validation noise.

Breaking errors this week (specific)

Phone could not reach our servers — App-blocking — 0 times, ~0 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 (65 → 25): user typed an incorrect or expired code — the SMS was delivered. Failure rate after submit: 7.2% (25/347).
SMS could not be sent (33 → 35): separate, more serious — user never gets a code. True login blocker.
OTP funnel this week: requested 393 → submitted 347 → succeeded 322.

Error overview Volume & source

Daily exceptions (Day 1–7 aligned)

This week peaked on Day 1 (17 exceptions on 2026-07-18).

Exceptions by SDK / source

Source	This week	Users	Prior week	Users
Mobile (posthog-react-native)	—	—	879	155
Backend (posthog-node)	17	1	174,513	39

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	17	1	174,206	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

-100.0% vs prior week

LoginOtpFailed (wrong code)

-61.5% vs prior week

SMS send failures

+6.1% 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

35 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.	393	319	802	555
Verification code entered User typed a code and tapped submit (includes retries).	347	308	562	483
Login succeeded Code was accepted and login completed.	322	306	498	476
Wrong or expired code Code rejected — SMS was sent; user can try again.	25	12	65	19

How to read these numbers

Events ≠ users. One person retrying a bad code many times creates many failure events. This week: 25 failures from 12 users. Prior week: 65 failures from 19 users.
User-level impact: only 3.4% of people who requested an SMS in the prior week (19 of 555) had at least one wrong-code failure. This week: 3.8% (12 of 319).
Submits > requests is normal — users often submit several times before getting it right.
Prior-week spike: 26 wrong-code events on 2026-07-10 from only 8 users — likely heavy retries or testing, not a mass login outage.
2 people in the prior week typed the wrong code 10+ times each — they account for most of the 65 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: Неправильный код. Запросите новый код или попробуйте снова	17	10
Произошла непредвиденная ошибка. Shown in app: Произошла непредвиденная ошибка.	6	2
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.	2	1

SMS send failures (this week)

Event	Message	Count	Users
ActionPhoneVerificationError	Could not send the verification code (SMS gateway or phone issue) Technical: Не удалось отправить код. Попробуйте снова.	21	6
ActionPhoneVerificationError	Calling the 'setValueWithKeyAsync' function has failed → Caused by: No keychain is available. You may need to restart your computer. Technical: Calling the 'setValueWithKeyAsync' function has failed → Caused by: No keychain is available. You may need to restart your computer.	12	1
ActionPhoneVerificationResendError	Could not send the verification code (SMS gateway or phone issue) Technical: Не удалось отправить код. Попробуйте снова.	2	1

Onboarding-related exceptions this week

Onboarding exception	Context	Breaking?	Occurrences	Users	Prior occ.	Prior users	Area
No onboarding-classified exceptions in top issues.

Step-blocking only (user can fix & retry)

Error	Context	Breaking?	Occurrences	Users	Prior occ.	Prior users	Area
No step-blocking issues in top set.