Error Report: 2026-03-20 (186 errors in last 24h)

[claude]

Summary

Authentication timeout classification bug persists for 12+ consecutive days requiring immediate fix. Backend Platform 428 errors continue affecting users trying to deploy to dashboard-created apps.

Metric	Value
Time range	last 24 hours
Total errors	186
CLI bugs	1
Backend issues	1
User errors (working as designed)	7
Unique users affected	94
Internal user occurrences	22

Errors requiring action

1. Authentication timeout lacks error classification — CLI bug

Error code	None (unclassified)
Occurrences	10 (0 internal)
Users affected	9
Command	whoami
Platforms	Linux
PostHog	View in error tracking
Existing issue	Referenced in #430, #426, #423, #416, #415
Recurring	Yes (12+ days)

Error: (from PostHog — the actual error message users see)

Error: Authentication timed out. Please try again.

Stack trace: (only showing frames from packages/cli/src/)

at waitForAuthentication (packages/cli/src/cli/commands/auth/login-flow.ts:71)
at login (packages/cli/src/cli/commands/auth/login-flow.ts:105)

Root cause: The authentication timeout throws a generic Error without proper classification:

// packages/cli/src/cli/commands/auth/login-flow.ts:69-74
} catch (error) {
  if (error instanceof Error && error.message.includes("timed out")) {
    throw new Error("Authentication timed out. Please try again.");
  }
  throw error;
}

This timeout occurs when the OAuth2 device code expires (line 60: timeout: expiresIn * 1000). The generic Error lacks proper classification for telemetry tracking, causing error_code: null and is_user_error: null in PostHog.

Suggested fix: In packages/cli/src/cli/commands/auth/login-flow.ts:71, replace throw new Error("Authentication timed out. Please try again.") with throw new AuthExpiredError("Authentication timed out. Please try again.") using the existing error class from packages/cli/src/core/errors.ts:147.

---

Backend issues (not CLI fixes)

Brief table of errors caused by the backend/server, not the CLI:

Error	Occurrences	Users	Command	PostHog
Backend Platform 428 requirement	38	21	deploy	View in error tracking

The 428 errors indicate users attempting to sync entities to dashboard-created apps that don't support Backend Platform features. The CLI correctly reports these server-side restrictions. Message: "This endpoint is only available for Backend Platform apps" affecting entity-schemas endpoint.

User errors (working as designed)

Brief table of expected user errors where the CLI validation is correct:

Error	Occurrences	Users	Command	PostHog
Functions not found in project (INVALID_INPUT)	43	18	functions deploy	View in error tracking
No Base44 project found (CONFIG_NOT_FOUND)	39	14	functions deploy	View in error tracking
Project already exists (CONFIG_EXISTS)	12	8	create	View in error tracking
Invalid app configuration schema (SCHEMA_INVALID)	9	8	deploy	View in error tracking
Deno dependency missing (DEPENDENCY_NOT_FOUND)	9	6	dev	View in error tracking
App not configured (CONFIG_INVALID)	7	5	deploy	View in error tracking
Function entry file not found (FILE_NOT_FOUND)	1	1	entities push	View in error tracking

All user errors provide appropriate validation messages and guidance. The functions not found error (43 occurrences) suggests users commonly reference non-existent functions like "ai_chat, ai_analyze_file" in their project configurations.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Authentication timeout (unclassified)	12+ days	Referenced in #430, #426, #423, #416, #415	No dedicated issue
Backend Platform 428 requirement	Ongoing	Previous error reports	Backend team aware

The authentication timeout classification bug has appeared in every daily error report since at least 2026-03-08 but remains unfixed, continuing to affect user experience and telemetry accuracy.

Action items

Numbered list of concrete next steps, most important first:

1. [critical] packages/cli/src/cli/commands/auth/login-flow.ts:71 — Replace throw new Error("Authentication timed out. Please try again.") with throw new AuthExpiredError("Authentication timed out. Please try again.") to enable proper telemetry classification. The AuthExpiredError class is already defined in packages/cli/src/core/errors.ts:147 and extends UserError with error code "AUTH_EXPIRED" and appropriate hints.

2. [medium] Monitor Backend Platform 428 errors — while not CLI bugs, the volume (38 occurrences, 21 users) suggests continued user confusion about CLI vs dashboard app capabilities. Consider improving error messaging or documentation to reduce friction during app migration.