Error Report: 2026-04-18 (190+ errors in last 24h)

[claude]

Summary

API deployment timeouts dominate the error landscape, with 60 authentication-related failures affecting backend operations. User validation errors continue at expected levels with appropriate CLI messaging. No critical CLI bugs identified.

Metric	Value
Time range	last 24 hours
Total errors	190+
CLI bugs	0
Backend issues	3
User errors (working as designed)	5
Unique users affected	59+
Internal user occurrences	8

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
API authentication failures (401)	60	8	functions list	View
Site deployment timeouts	51	25+	site deploy, deploy	View
Entity sync platform restrictions (428)	4	3	entities push, deploy	View

Authentication failures analysis: The CLI properly reports 401 Unauthorized errors when credentials are invalid or expired. From packages/cli/src/core/site/api.ts:29, the ApiError.fromHttpError() method correctly extracts and formats server error messages like "Could not validate credentials".

Deployment timeout analysis: The CLI 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" indicating backend infrastructure performance issues.

Backend Platform restriction analysis: The CLI correctly reports 428 Precondition Required when users try to access Backend Platform features with incompatible app types. Server returns appropriate error messages like "This endpoint is only available for Backend Platform apps".

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Project not found validation	47	18	deploy	View
Non-interactive mode validation	46	16	deploy	View
Schema validation errors	10	6	functions deploy	View
Project already linked	5	4	link	View
Authentication timeout	5	5	agents pull	View

CONFIG_NOT_FOUND analysis: From packages/cli/src/core/project/config.ts:75-77, when findProjectRoot() returns null (no config.jsonc found), the CLI throws clear guidance: "Project root not found. Please ensure config.jsonc or config.json exists in the project directory."

INVALID_INPUT analysis: Various validation patterns including --yes flag requirements ("--yes is required in non-interactive mode"), missing path arguments, and duplicate function names all provide appropriate error messaging with clear guidance.

SCHEMA_INVALID analysis: Configuration validation errors show specific field-level guidance like "Invalid input: expected string, received undefined → at id" which helps users fix their configuration files.

CONFIG_EXISTS analysis: Users trying to link already-linked projects get clear validation from the CLI with appropriate guidance about existing project configuration.

AUTH_EXPIRED analysis: Authentication timeout handling provides clear guidance with "Authentication timed out. Please try again." from the CLI's authentication flow.

Recurring errors

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

Error	Days recurring	Existing issue	Tracked?
Deployment API timeouts	6+ days	Referenced in #485, #483, #478, #476	Yes (backend infrastructure)
CONFIG_NOT_FOUND validation	7+ days	Referenced in #485, #483, #479, #478, #476	Yes (expected user error)
INVALID_INPUT validation	7+ days	Referenced in #485, #483, #479, #478, #476	Yes (expected user error)
Authentication failures	6+ days	Referenced in #485, #483, #479, #478	Yes (backend/credential issue)
Schema validation errors	6+ days	Referenced in #485, #483, #479, #478, #476	Yes (expected user error)

The deployment timeout issue remains the primary technical concern and represents a backend infrastructure bottleneck affecting user experience.

Action items

Backend infrastructure priorities requiring server-side attention:

1. [high] Investigate deployment API timeout issues affecting 51 occurrences across 25+ users during site deployment operations — backend performance optimization needed
2. [medium] Review authentication credential validation errors (60 occurrences) — may indicate token refresh issues or credential sync problems
3. [low] Consider increasing 3-minute deployment timeout in packages/cli/src/core/site/api.ts:26 or implementing progress feedback for long deployments

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.