Le-Ko — PostHog error health snapshot

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

Current period: 27 Jul – 02 Aug 2026 · Comparison: 20 Jul – 26 Jul 2026
Report generated: 03 August 2026 · Source: PostHog Error Tracking ($exception + onboarding events)

Executive summary PostHog Error Tracking

Total exceptions

n/a

Users affected

n/a

Distinct issues

n/a

$exception ingestion looks dead (both weeks at 0)

Both weeks show 0 $exception events. OTP/SMS custom events still fire, so product telemetry is alive — only Error Tracking exception capture appears broken.

Breaking errors this week (specific)

No $exception events in either comparison week — Error Tracking issue tables/charts are empty. Last non-zero week in Production was w/c 13 Jul (very high volume), then ingestion dropped to zero from 20 Jul onward. Do not read this as “zero production errors.”

Login / OTP (not the same as SMS failure)

Wrong verification code (17 → 32): user typed an incorrect or expired code — the SMS was delivered. Failure rate after submit: 5.3% (32/602).
SMS could not be sent (36 → 75): separate, more serious — user never gets a code. True login blocker. Users affected: 8 → 25.
OTP funnel this week: requested 743 → submitted 602 → succeeded 570.

Error overview Volume & source

Daily exceptions (Day 1–7 aligned)

This week peaked on Day — (— exceptions on ).

Exceptions by SDK / source

Source	This week	Users	Prior week	Users
Mobile (posthog-react-native)	—	—	—	—
Backend (posthog-node)	—	—	—	—

Most common errors By issue

Where errors happen

No exception issues to classify — $exception volume is zero. Use the OTP/SMS section below for login reliability; restore Error Tracking ingestion before trusting this table.

Top issues this week (by occurrences)

Error	Context	Breaking?	Occurrences	Users	Prior occ.	Prior users	Area

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

n/a

LoginOtpFailed (wrong code)

+88.2% vs prior week

SMS send failures

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

75 SMS-send failure events from 25 users this week (was 36 events / 8 users). 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.	743	602	351	285
Verification code entered User typed a code and tapped submit (includes retries).	602	557	310	273
Login succeeded Code was accepted and login completed.	570	555	293	271
Wrong or expired code Code rejected — SMS was sent; user can try again.	32	12	17	13

How to read these numbers

Events ≠ users. One person retrying a bad code many times creates many failure events. This week: 32 failures from 12 users. Prior week: 17 failures from 13 users.
User-level impact: only 4.6% of people who requested an SMS in the prior week (13 of 285) had at least one wrong-code failure. This week: 2.0% (12 of 602).
Submits > requests is normal — users often submit several times before getting it right.
Prior-week spike: 4 wrong-code events on 2026-07-24 from only 4 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
Неправильный код. Запросите новый код или попробуйте снова Shown in app: Неправильный код. Запросите новый код или попробуйте снова	22	10
Произошла непредвиденная ошибка. Shown in app: Произошла непредвиденная ошибка.	8	1
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.	1	1
O código não está correto. Solicite outro código ou tente novamente. Shown in app: O código não está correto. Solicite outro código ou tente novamente.	1	1

SMS send failures (this week)

Event	Message	Count	Users
ActionPhoneVerificationError	Could not send the verification code (SMS gateway or phone issue) Technical: Не удалось отправить код. Попробуйте снова.	58	21
ActionPhoneVerificationResendError	Could not send the verification code (SMS gateway or phone issue) Technical: Не удалось отправить код. Попробуйте снова.	11	3
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.	3	1
ActionPhoneVerificationResendError	— Technical: —	2	1
ActionPhoneVerificationError	— Technical: —	1	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.