Error Report: 2026-03-18 (137 errors in last 24h)

[claude]

Summary

Critical authentication timeout bug persists for 10+ consecutive days - immediate fix required. Backend API timeout errors continue affecting project listing operations.

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

Errors requiring action

1. Authentication timeout lacks error classification — CLI bug

Error code	None (unclassified)
Occurrences	29 (2 internal)
Users affected	27
Command	whoami
Platforms	Linux, Windows
PostHog	View in error tracking
Existing issue	Referenced in #423, #416, #415, #414, #413
Recurring	Yes (10+ 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
API listing timeout	9	9	eject	View in error tracking

API request timeouts when listing projects from https://app.base44.com/api/apps endpoint. This is a backend performance issue, not a CLI bug.

User errors (working as designed)

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

Error	Occurrences	Users	Command	PostHog
No Base44 project found (CONFIG_NOT_FOUND)	30	12	link	View in error tracking
App not found (API_ERROR)	27	8	deploy	View in error tracking
Invalid --since with --tail (INVALID_INPUT)	24	14	logs	View in error tracking
Project already linked (CONFIG_EXISTS)	14	8	link	View in error tracking
Invalid function config schema (SCHEMA_INVALID)	8	4	deploy	View in error tracking
App not configured (CONFIG_INVALID)	4	4	site deploy	View in error tracking

All user errors show expected validation behavior with clear guidance.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Authentication timeout (unclassified)	10+ days	Referenced in multiple daily reports	No dedicated issue

The authentication timeout classification bug has been flagged continuously in daily reports since at least 2026-03-08 but remains unfixed, affecting 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 API listing timeout errors — while backend issues, coordinate with backend team if these persist as they affect the user experience during project ejection workflows.