Error Report: 2026-04-22 (211 errors in last 24h)

[claude]

Summary

User validation errors continue at expected levels with appropriate CLI messaging. Backend API entity sync restrictions affect 19 occurrences. All CLI error handling working correctly with clear user guidance. No CLI bugs requiring immediate action.

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

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
Entity schema deletion restrictions (428)	19	13	deploy, entities push	View in error tracking

Entity sync restriction analysis: The CLI correctly makes PUT requests to the backend entity-schemas endpoint via syncEntities() in packages/cli/src/core/resources/entity/api.ts:20. The backend returns 428 Precondition Required with messages like "Cannot delete entity schema for 'LangSetting': it has existing records" when users try to remove entity schemas that have data. The CLI properly reports these via ApiError.fromHttpError() at line 27. This is working backend business logic, not a CLI issue.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Project not found validation	57	28	link, deploy	View
Non-interactive mode validation	45	16	site deploy	View
Entity schema validation	14	7	entities push	View
Authentication timeout	12	12	connectors pull	View
Project already linked	8	6	link	View
App configuration missing	7	3	functions deploy	View
Deno dependency missing	4	4	exec	View
Duplicate resource names	18+	15+	entities push, eject	Multiple PostHog links

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 or base44/ subdirectory." This is working as designed.

INVALID_INPUT analysis: Multiple validation patterns including --yes flag requirements ("--yes is required in non-interactive mode" and "--project-id is required in non-interactive mode"), missing build directories ("Output directory does not exist: . Make sure to build your project first."), and duplicate function/agent names all provide appropriate error messaging.

SCHEMA_INVALID analysis: Entity and agent schema validation from Zod provides specific field-level guidance like "Invalid input: expected string, received undefined → at name" and "Invalid input → at tool_configs[3]" which helps users fix their configuration files.

AUTH_EXPIRED analysis: Authentication timeout handling from packages/cli/src/core/errors.ts:147-163 provides clear guidance with "Authentication timed out. Please try again." directing users to re-authenticate.

CONFIG_EXISTS analysis: Users trying to link already-linked projects get clear validation from packages/cli/src/core/errors.ts:216-229: "Project is already linked. An .app.jsonc file with the appId already exists."

CONFIG_INVALID analysis: App configuration validation provides guidance: "App not configured. Create a .app.jsonc file or run 'base44 link' to link this project." This is appropriate for unlinked projects.

DEPENDENCY_NOT_FOUND analysis: From packages/cli/src/core/errors.ts:268-279, the CLI properly validates Deno installation and provides clear guidance: "Deno is required to run scripts with exec" when the dependency is missing.

Environment issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
File system permission errors	13	2	link	View

File system permission analysis: Error shows "EPERM: operation not permitted, scandir 'C:\Users\USER\Application Data'" with empty stack trace from Node.js. This is a Windows file system permissions issue where Node.js cannot read certain system directories, not a CLI bug. The CLI is not directly calling scandir - this is internal Node.js filesystem behavior during file operations.

Recurring errors

Based on previous daily reports (issues #490, #489, #488, #486, #485), these errors continue from multiple days:

Error	Days recurring	Existing issue	Tracked?
CONFIG_NOT_FOUND validation	10+ days	Referenced in #490, #489, #488, #486, #485	Yes (expected user error)
INVALID_INPUT validation	10+ days	Referenced in #490, #489, #488, #486, #485	Yes (expected user error)
Entity sync restrictions (428)	2+ days	Referenced in #490	Yes (backend business rules)
Authentication timeout	9+ days	Referenced in #490, #489, #488, #486, #485	Yes (expected timeout)
Schema validation errors	9+ days	Referenced in #490, #489, #488, #486, #485	Yes (expected user error)
Dependency validation	9+ days	Referenced in #490, #489, #488, #486, #485	Yes (expected user error)

All recurring errors are expected user validation patterns or documented backend business rules. No new error categories requiring investigation.

Action items

No CLI code changes required. Backend business rule for entity schema protection is working as designed:

1. [low] Entity schema deletion restrictions (428 errors) represent backend data protection - users attempting to remove entity schemas with existing records receive appropriate error messages via the CLI's standard API error handling