Error Report: 2026-03-22 (193 errors in last 24h)

[claude]

Summary

Authentication timeout classification bug persists for 14+ consecutive days requiring immediate fix. Backend API timeout continues as highest-volume issue affecting deployments.

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

Errors requiring action

1. Authentication timeout lacks error classification — CLI bug

Error code	None (unclassified)
Occurrences	4 (0 internal)
Users affected	4
Command	login
Platforms	Darwin
PostHog	View in error tracking
Existing issue	Referenced in #434, #433, #430, #426, #423
Recurring	Yes (14+ 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)

Error	Occurrences	Users	Command	PostHog
API timeout errors	97	12	deploy	View

The highest-volume error is API timeouts during site deployment: "Request timed out: POST https://app.base44.com/api/apps/.../deploy-dist". This affects 12 users with 61 occurrences from the top error group alone. These are backend infrastructure timeouts, not CLI bugs.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Duplicate function names	45	11	eject	View
No Base44 project found	24	9	dev, exec, link	View
App not configured	11	5	entities push, logs	View
Project already exists	8	6	eject, link	View
Non-interactive mode validation	7	7	eject, link	Various links
Invalid function config schema	2	2	deploy	View
Deno dependency missing	1	1	exec	View

All user errors provide appropriate validation messages and guidance. The high volume of "No Base44 project found" errors (24 occurrences) suggests users commonly run commands outside project directories.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Authentication timeout (unclassified)	14+ days	Referenced in #434, #433, #430, #426, #423	No dedicated issue

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

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 API timeout issues — while not CLI bugs, the volume (97 occurrences, 12 users) suggests backend performance degradation during site deployments. Consider coordination with backend team if these persist.