Error Report: 2026-02-19 (9 errors in last 48h)

[claude]

Summary

The last 48 hours show 394 total errors across 9 error types affecting 146 unique users. Critical issues include function deployment timeouts, authentication failures, and widespread user configuration errors. All major error types are recurring from the previous report, indicating persistent infrastructure and UX problems.

Metric	Value
Time range	last 48 hours
Total errors	394
CLI bugs	121
Backend issues	87
User errors (working as designed)	147
Build failures (needs investigation)	39
Unique users affected	146
Internal user occurrences	62

Errors requiring action

1. Function Deployment Timeout Issues — CLI bug

Error code	API_ERROR
Occurrences	105 (29 internal)
Users affected	39
Command	site deploy, functions deploy
Platforms	macOS, Windows, Linux
PostHog	View in error tracking
Existing issue	None
Recurring	Yes (2+ days)

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

ApiError: Function deployment errors:
'notify-slack' function: Deno deployment failed: Operation wait_for_deployment(notify-slack) timed out after 90 seconds

Stack trace: (only frames from src/)

at runCLI (src/cli/index.ts:32:4)

Root cause: (from CLI code — includes code snippet)

// src/core/resources/function/api.ts:29-32
response = await appClient.put("backend-functions", {
  json: payload,
  timeout: false, // No client-side timeout - problematic for long deployments
});

Function deployment errors are collected and re-thrown as ApiError in the CLI:

// src/cli/commands/functions/deploy.ts:41-50
if (result.errors && result.errors.length > 0) {
  const errorMessages = result.errors
    .map((e) => `'${e.name}' function: ${e.message}`)
    .join("\n");
  throw new ApiError(`Function deployment errors:\n${errorMessages}`);
}

Suggested fix: Add configurable client-side timeout in src/core/resources/function/api.ts:31 and implement retry logic for deployment operations that exceed reasonable limits.

---

2. Authentication Timeout Generic Errors — CLI bug

Error code	None (generic Error)
Occurrences	16 (0 internal)
Users affected	16
Command	whoami, login, create
Platforms	Windows, Linux
PostHog	View in error tracking
Existing issue	None
Recurring	Yes (2+ days)

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

Error: Authentication timed out. Please try again.

Stack trace: (only frames from src/)

at runCLI (src/cli/index.ts:32:4)

Root cause: (from CLI code — includes code snippet)

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

Suggested fix: Replace generic Error with proper AuthenticationTimeoutError class in src/cli/commands/auth/login-flow.ts:71 to provide consistent error handling and better recovery guidance.

---

3. Build Failures During Eject — needs investigation

Error code	None
Occurrences	39 (4 internal)
Users affected	36
Command	eject
Platforms	macOS, Linux
PostHog	No issue_id available
Existing issue	None
Recurring	Yes (2+ days)

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

Command failed with exit code 1: 'npm run build'

[vite:load-fallback] Could not load /src/entities/Benchmark (imported by src/pages/Benchmark.jsx): ENOENT: no such file or directory, open '/src/entities/Benchmark'

Stack trace: (only frames from src/)
Root cause not found in CLI code — may be a backend/infrastructure issue

Suggested fix: Investigate the eject workflow to understand why build commands fail after project ejection, particularly around entity file resolution.

---

Backend issues (not CLI fixes)

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

Error	Occurrences	Users	Command	PostHog
API 428 - Backend Platform only	18	18	entities push, site deploy	link
API 422 - Function validation failure	9	9	functions deploy	link
Function deployment parsing errors	5	5	functions deploy	link

These are server-side validation and configuration issues that may need backend team attention.

User errors (working as designed)

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

Error	Occurrences	Users	Command	PostHog
CONFIG_NOT_FOUND - outside project dir	91	35	deploy, link, dev	link
SCHEMA_INVALID - invalid entity files	46	26	deploy, entities push	link
CONFIG_EXISTS - project already linked	34	21	link	link
CONFIG_INVALID - missing app config	27	14	entities push, functions deploy	link
INVALID_INPUT - invalid project ID	26	13	eject, link	link
FILE_NOT_FOUND - deploy without build	19	13	site deploy	link
DEPENDENCY_NOT_FOUND - Deno missing	2	1	dev	No PostHog link

High volume of CONFIG_NOT_FOUND errors (91 occurrences) suggests users frequently run commands outside project directories, indicating potential UX improvements needed for project discovery guidance.

Recurring errors

All major errors from the previous daily report are recurring:

Error	Days recurring	Existing issue	Tracked?
Function deployment API_ERROR	2+ days	#273	mentioned only
CONFIG_NOT_FOUND (high volume)	2+ days	#273	mentioned only
Authentication timeouts	2+ days	#273	mentioned only
FILE_NOT_FOUND (site deployment)	2+ days	#273	mentioned only
SCHEMA_INVALID	2+ days	#273	mentioned only

All critical system errors continue to recur, indicating persistent issues requiring immediate attention.

Action items

Numbered list of concrete next steps, most important first:

1. [critical] src/core/resources/function/api.ts:31 — Replace timeout: false with configurable timeout (e.g., 120 seconds) and add retry logic for deployment operations
2. [high] src/cli/commands/auth/login-flow.ts:71 — Replace generic Error with AuthenticationTimeoutError class and add error code for proper CLI error handling
3. [high] Investigate eject build failures — missing entity files suggest project scaffold issues after ejection
4. [medium] src/core/project/config.ts:74 — Add better guidance for CONFIG_NOT_FOUND errors with directory suggestions or base44 init command hints
5. [medium] Add base44 entities validate command to help users fix SCHEMA_INVALID errors before deployment attempts