Error Report: 2026-04-19 (179 errors in last 24h)

[claude]

Summary

Backend network issues dominate the error landscape with deployment timeouts and connection failures. User validation errors continue at expected levels with appropriate CLI messaging. No critical CLI bugs identified - all errors show proper error handling and clear user guidance.

Metric	Value
Time range	last 24 hours
Total errors	179
CLI bugs	0
Backend issues	2
User errors (working as designed)	7
Unique users affected	58+
Internal user occurrences	5

Errors requiring action

No CLI bugs requiring immediate action. All errors show appropriate validation and error handling.

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Deployment API timeouts	46	19+	deploy, site deploy	View
Network connection failures	9	7	deploy	None (raw network errors)

Deployment timeout analysis: The CLI correctly configures a 3-minute timeout for deployment operations (packages/cli/src/core/site/api.ts:26), but the backend deployment API frequently exceeds this limit. Error messages show "Request timed out: POST https://app.base44.com/api/apps/.../deploy-dist" and "fetch failed" indicating backend infrastructure performance issues, not CLI problems.

Network connection analysis: Low-level network errors like "read ECONNRESET", "fetch failed", and "Headers Timeout Error" originate from Node.js HTTP stack when backend connections fail. The CLI properly propagates these via ApiError.fromHttpError() in packages/cli/src/core/errors.ts:335-384.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Non-interactive mode validation	39	10	deploy	View
Project not found validation	26	8	link	View
Authentication timeout	11	11	entities push	View
Deno dependency missing	10	2	exec	View
App configuration errors	4	4	entities push	View
Entity schema validation	2	1	entities push	View
Project already linked	2	2	link	View

INVALID_INPUT analysis: From packages/cli/src/core/project/config.ts:75-77, when users run commands in non-interactive mode without required flags like --yes, the CLI provides clear validation: "--yes is required in non-interactive mode". This is working as designed.

CONFIG_NOT_FOUND analysis: When findProjectRoot() returns null (no config.jsonc found), the CLI throws clear guidance via ConfigNotFoundError in packages/cli/src/core/project/config.ts:75-77: "No Base44 project found. Run this command from a project directory with a config.jsonc file."

AUTH_EXPIRED analysis: Authentication timeout handling provides clear guidance with "Authentication timed out. Please try again." from the CLI's authentication flow, properly directing users to re-authenticate.

DEPENDENCY_NOT_FOUND analysis: The CLI properly validates Deno installation and provides clear guidance: "Deno is required to run scripts with exec" when the dependency is missing for script execution.

SCHEMA_INVALID analysis: Entity validation shows specific field-level guidance like the entity type validation errors, helping users fix their entity schema files with clear error messages.

Recurring errors

Based on previous daily reports (issues #486, #485, #483, #479, #478), these errors continue from multiple days:

Error	Days recurring	Existing issue	Tracked?
Deployment API timeouts	7+ days	Referenced in #486, #485, #483, #479, #478	Yes (backend infrastructure)
CONFIG_NOT_FOUND validation	8+ days	Referenced in #486, #485, #483, #479, #478	Yes (expected user error)
INVALID_INPUT validation	8+ days	Referenced in #486, #485, #483, #479, #478	Yes (expected user error)
Authentication timeout	7+ days	Referenced in #486, #485, #483, #479, #478	Yes (expected timeout)
Network connection failures	6+ days	Referenced in #486, #485, #483, #479	Yes (infrastructure issue)

The deployment timeout and network connectivity issues remain the primary technical concerns representing backend infrastructure bottlenecks affecting user experience.

Action items

Backend infrastructure priorities requiring server-side attention:

1. [high] Investigate deployment API timeout issues affecting 46 occurrences across 19+ users during site deployment operations — backend performance optimization needed
2. [medium] Review network connection stability affecting 9+ users with ECONNRESET and fetch failures — may indicate load balancer or infrastructure issues

All user validation errors show appropriate CLI behavior with clear error messages and actionable guidance. CLI error handling is working correctly across all error categories.