Error Report: 2026-02-25 (204 errors in last 24h)

[claude]

Summary

One potential CLI bug identified for investigation: TypeError during eject command reading undefined 'disabled' property. Most other errors are persistent backend infrastructure issues (deployment timeouts) or expected user validation errors with consistent volumes from previous reports.

Metric	Value
Time range	last 24 hours
Total errors	204
CLI bugs	1
Backend issues	4
User errors (working as designed)	6
Unique users affected	61
Internal user occurrences	81

Errors requiring action

1. TypeError during eject command — needs investigation

Error code	None
Occurrences	2 (0 internal)
Users affected	2
Command	eject
Platforms	Windows
PostHog	View in error tracking
Existing issue	None
Recurring	No

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

TypeError: Cannot read properties of undefined (reading 'disabled')

Stack trace: (only show frames from src/)

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

Root cause: The stack trace is too shallow to identify the specific location of this TypeError. The error indicates that some object is undefined when the code tries to access its disabled property during the eject command execution. Without more detailed stack frames from the eject command logic, the root cause cannot be determined from the available error data.

Suggested fix: Add more detailed error tracking to the eject command or investigate the eject command flow to identify where the disabled property is accessed without null checking.

---

Backend issues (not CLI fixes)

Backend infrastructure issues that need server-side attention:

Error	Occurrences	Users	Command	PostHog
Function deployment timeouts (API_ERROR)	84 (2 internal)	20	functions deploy	link
Site deployment timeouts (API_ERROR)	33 (67 internal)	13	site deploy, deploy	link
Backend Platform availability errors	13 (5 internal)	8	functions deploy, entities push	link
Authentication/OAuth errors	2 (0 internal)	2	create	link

Function deployment timeouts (84 occurrences): Deno deployment operations consistently timing out after 90 seconds with messages like "Operation wait_for_deployment(evaluate-description) timed out after 90 seconds". The CLI correctly handles this by setting timeout: false in the HTTP client and reporting server-side timeout messages.

Site deployment timeouts (33 occurrences): HTTP requests to POST /api/apps/{id}/deploy-dist timing out during site upload operations. The CLI sets a 180-second timeout, but these are server-side timeouts affecting the deployment process.

Backend Platform availability (13 occurrences): HTTP 428 responses with "This endpoint is only available for Backend Platform apps" and HTTP 409 "Another deployment is in progress" errors. These are working as designed but suggest either user confusion about app types or deployment concurrency issues.

User errors (working as designed)

Expected user errors where CLI validation is correct:

Error	Occurrences	Users	Command	PostHog
No project found (CONFIG_NOT_FOUND)	29 (5 internal)	19	deploy, link, functions deploy, entities push, dashboard open	link
Project already linked (CONFIG_EXISTS)	6 (0 internal)	4	link	link
Invalid entity schemas (SCHEMA_INVALID)	17 (4 internal)	11	site deploy, deploy	link
Missing app config (CONFIG_INVALID)	7 (0 internal)	6	entities push, functions deploy	link
Invalid project ID (INVALID_INPUT)	5 (1 internal)	5	link, logs	link
Missing build output (FILE_NOT_FOUND)	3 (0 internal)	3	deploy	link

CONFIG_NOT_FOUND (29 occurrences) remains the highest-volume user error, indicating users running commands outside project directories. The CLI correctly validates and provides helpful guidance:

// src/core/errors.ts:151-172
export class ConfigNotFoundError extends UserError {
  readonly code = "CONFIG_NOT_FOUND";
  constructor(message = "No Base44 project found in this directory", options?: CLIErrorOptions) {
    super(message, {
      hints: options?.hints ?? [
        { message: "Run 'base44 create' to create a new project", command: "base44 create" },
        { message: "Or run 'base44 link' to link an existing project", command: "base44 link" },
      ],
      cause: options?.cause,
    });
  }
}

SCHEMA_INVALID (17 occurrences) shows users with invalid entity definitions. The CLI provides detailed validation messages with file paths and specific error locations.

Authentication timeout (9 occurrences from summary) occur within OAuth2 device code flow limits. The CLI correctly handles this with proper timeout detection:

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

FILE_NOT_FOUND (3 occurrences) occur when users deploy without building first. The error message correctly suggests building the project first.

Recurring errors

Comparing with recent daily reports (issues #324, #312, #283, #281, #280):

Error	Days recurring	Existing issue	Tracked?
Function deployment timeouts (API_ERROR)	6+ days	error-reports only	partially
CONFIG_NOT_FOUND (high volume)	6+ days	error-reports only	partially
Site deployment timeouts (API_ERROR)	6+ days	error-reports only	partially
Authentication timeouts	6+ days	error-reports only	partially
SCHEMA_INVALID	6+ days	error-reports only	partially
CONFIG_EXISTS	6+ days	error-reports only	partially
FILE_NOT_FOUND (deploy)	6+ days	error-reports only	partially

All major error patterns continue to recur across 6+ consecutive days with stable volumes. Function deployment timeout issues have been consistently reported since at least issue #280, indicating persistent backend infrastructure challenges affecting Deno Deploy operations.

The TypeError during eject is new in this report and was not seen in previous reports.

Action items

1. [medium] Investigate TypeError in eject command - add debugging or better error tracking to identify where undefined.disabled access occurs
2. [low] Monitor function deployment timeout patterns - this is a persistent backend infrastructure issue consistently affecting user workflows across 6+ consecutive days
3. [low] Consider tracking Backend Platform availability error patterns to determine if documentation improvements are needed

Notes

• One potential CLI bug identified - the TypeError during eject command needs investigation, though impact is low (2 occurrences)
• Stable recurring patterns - error types and volumes very consistent with previous 6 daily reports
• High internal user ratio (81 out of 204 total errors) suggests good internal testing coverage and usage
• Backend infrastructure challenges - function deployment timeouts remain the primary persistent system issue affecting user experience
• Good error handling - CLI provides clear validation messages with actionable hints for all user errors