Error Report: 2026-03-23 (135 errors in last 24h)

[claude]

Summary

Authentication timeout classification bug persists for 15+ consecutive days requiring immediate fix. Backend function logs API errors now dominate error volume with 35 occurrences affecting 11 users.

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

Errors requiring action

1. Authentication timeout lacks error classification — CLI bug

Error code	None (unclassified)
Occurrences	12 (0 internal)
Users affected	12
Command	create
Platforms	Various
PostHog	View in error tracking
Existing issue	Referenced in #436, #434, #433, #430, #426
Recurring	Yes (15+ 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
Function logs API 500 error	35	11	logs	View

The highest-volume error is backend API failures when fetching function logs: "Request failed with status code 500 Internal Server Error: GET https://app.base44.com/api/apps/.../functions-mgmt/askTourAssistant/logs". Backend error message shows: "Error fetching function logs: 'askTourAssistant': 'NoneType' object has no attribute 'get_logs'" - a Python server-side error where a None object is being accessed. This affects users trying to view logs for the askTourAssistant function.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Non-interactive mode validation	19	9	link	Various
No Base44 project found	18	8	dev	View
Project already linked	6	4	link	Various
App not configured	4	2	entities push	Various
Invalid function config schema	3	2	deploy	Various
Deno dependency missing	3	3	exec	Various

All user errors provide appropriate validation messages and guidance. The CLI correctly validates required flags in non-interactive mode and project directory requirements.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Authentication timeout (unclassified)	15+ days	Referenced in #436, #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. This is now the longest-running unresolved error in the CLI.

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] Coordinate with backend team on function logs API failures — 35 occurrences affecting 11 users suggests the askTourAssistant function's log retrieval is consistently failing with NoneType errors. This may require backend investigation.