Error Report: 2026-04-03 (202 errors in last 24h)

[claude]

Summary

Backend platform requirement errors dominate API failures with 17 occurrences affecting site deployments. User validation errors continue at expected volumes with appropriate messaging. Network connectivity issues appear in 6 cases suggesting environment problems rather than CLI bugs.

Metric	Value
Time range	last 24 hours
Total errors	202
CLI bugs	0
Backend issues	1
User errors (working as designed)	8
Unique users affected	96
Internal user occurrences	1

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Backend Platform app requirements	17	12	site deploy	link

Backend Platform Requirements: The CLI correctly calls the site deployment API but receives HTTP 428 responses with message "This endpoint is only available for Backend Platform apps". This indicates users are trying to deploy sites from apps that were created through the web UI rather than via the CLI. The CLI properly handles this error with structured messaging.

Root cause analysis: From the API error handling in packages/cli/src/core/errors.ts:432-441, the CLI already provides targeted hints for the requires_backend_platform_app reason code, suggesting users remove .app.jsonc and re-link to CLI-created apps. This is working as designed but indicates a user education gap about app types.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
No Base44 project found	59	20	link	link
Missing required parameters	53	19	eject	link
Authentication timeout	15	15	functions deploy	link
App not configured	12	9	deploy	link
Invalid configuration schema	11	7	deploy	link
Project already exists	6	5	create	link
Network connectivity failures	6	6	login	None (issue_id is null)
Deno dependency missing	3	2	exec	link

CONFIG_NOT_FOUND analysis: From packages/cli/src/core/project/config.ts:74-78, the CLI correctly throws ConfigNotFoundError when users run commands outside Base44 project directories. Error message includes appropriate hints to run base44 create or base44 link.

CONFIG_INVALID analysis: From packages/cli/src/core/project/app-config.ts:56-68, the CLI correctly validates that .app.jsonc files contain a valid app ID and provides guidance to run base44 link when missing.

Authentication timeouts: From packages/cli/src/cli/commands/auth/login-flow.ts:74-77, the CLI correctly detects OAuth flow timeouts and wraps them with AuthExpiredError. The 15 occurrences suggest normal authentication service latency.

Network failures: The 6 instances of "fetch failed" and "ENOTFOUND" errors indicate DNS/connectivity issues in user environments rather than CLI bugs.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Backend Platform app requirements	4+ days	Referenced in #458, #457	No dedicated issue
CONFIG_NOT_FOUND validation	5+ days	Referenced in #459, #458, #457, #456, #451	No dedicated issue
Authentication timeouts	5+ days	Referenced in #459, #458, #457, #456, #451	No dedicated issue

Backend Platform requirements: This error pattern has been appearing consistently across multiple daily reports, indicating users frequently attempt to deploy sites from web UI-created apps to CLI endpoints that require Backend Platform apps.

CONFIG_NOT_FOUND pattern: Consistently high volume (46-59 occurrences daily) indicates users regularly attempt Base44 commands outside project directories. Error messaging is appropriate and working as designed.

Authentication timeout consistency: 10-15 occurrences daily suggest normal OAuth service performance variability rather than a systemic issue.

Action items

1. [low] Consider documentation improvements around Backend Platform app requirements vs web UI-created apps to reduce the 17 daily occurrences of 428 errors
2. [low] Monitor network connectivity error pattern (6 occurrences) to determine if environmental factors are affecting user authentication flows