Error Report: 2026-04-16 (267 errors in last 24h)

[claude]

Summary

User validation errors dominate with expected behavior and clear CLI messaging. Backend Platform app restrictions generate moderate API error volume. All CLI error handling is working correctly with appropriate validation messages. No CLI bugs requiring immediate action.

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

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
Backend Platform app requirement (428)	52	21	deploy	View

Backend Platform restriction analysis: The CLI correctly reports 428 Precondition Required when users try to access Backend Platform features (entity schemas, site deployment) with incompatible app types. From packages/cli/src/core/errors.ts:339-374, the ApiError.fromHttpError method properly extracts server error messages like "This endpoint is only available for Backend Platform apps" and "Error syncing entities: Invalid User schema: User schema cannot contain base fields: email, full_name."

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
No input provided to exec	69	33	exec	View
No Base44 project found	46	20	dev	View
App not configured	29	17	deploy	View
Entity schema validation errors	25	12	deploy	View
Authentication timed out	15	15	whoami	View
Project already linked	14	8	link	View
Deno dependency missing	13	11	dev	View
Various input validation errors	13+	22+	link, eject, deploy	Multiple PostHog links

INVALID_INPUT analysis: From packages/cli/src/core/errors.ts:169-190, the ConfigNotFoundError is properly triggered when findProjectRoot() returns null in packages/cli/src/core/project/config.ts:74-77. Users running base44 exec without piping script content get clear validation: "No input provided. Pipe a script to stdin."

CONFIG_NOT_FOUND analysis: From packages/cli/src/core/project/config.ts:75-77, when no config.jsonc file is found in the directory tree, the CLI throws ConfigNotFoundError with guidance: "Project root not found. Please ensure config.jsonc or config.json exists in the project directory."

CONFIG_INVALID analysis: App configuration validation errors show specific field-level errors like "Invalid input: expected string, received undefined → at id" and "App not configured. Create a .app.jsonc file or run 'base44 link' to link this project."

SCHEMA_INVALID analysis: Entity file validation errors show specific validation failures like "Field condition values must be a primitive or an operator object ($in, $nin, $ne, $all) → at rls.read" which provides clear guidance for fixing entity schema files.

AUTH_EXPIRED analysis: Authentication timeout errors provide clear guidance with "Authentication timed out. Please try again." and appropriate hints for re-authentication.

CONFIG_EXISTS analysis: From the error data, users trying to link already-linked projects get clear validation: "Project is already linked. An .app.jsonc file with the appId already exists."

DEPENDENCY_NOT_FOUND analysis: From packages/cli/src/core/utils/dependencies.ts, the CLI properly validates Deno installation and provides installation guidance when missing for backend function execution.

Network issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
OAuth device code timeout	4	4	deploy	None (issue_id null)

Network connectivity issues during device code flow causing "Request timed out: POST https://app.base44.com/oauth/device/code". This is infrastructure-related, not a CLI bug.

Recurring errors

Based on previous daily reports, these errors continue from multiple days:

Error	Days recurring	Existing issue	Tracked?
CONFIG_NOT_FOUND validation	6+ days	Referenced in #479, #478, #476, #474, #473	Yes (expected user error)
INVALID_INPUT validation	6+ days	Referenced in #479, #478, #476, #474, #473	Yes (expected user error)
Backend Platform app requirement	5+ days	Referenced in #478, #476, #474, #472	Yes (backend restriction)
Authentication timeout	5+ days	Referenced in #479, #478, #476, #474, #473	Yes (expected timeout)
Schema validation errors	5+ days	Referenced in #479, #478, #476, #474, #473	Yes (expected user error)

All recurring errors show consistent, expected patterns. No untracked CLI bugs in today's data.

Action items

No critical CLI action items. All errors show appropriate validation and error handling:

1. [info] Backend Platform app restrictions (52 occurrences) are working as designed but continue to affect users trying to access premium features with basic app types

2. [info] Input validation errors (69 occurrences) provide appropriate guidance but suggest users need better understanding of command requirements in non-interactive mode

3. [info] Config validation errors (75 total occurrences) are properly handled but high volume suggests onboarding documentation could be improved

The CLI error handling and user messaging are working correctly across all error categories.