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

[claude]

Summary

User validation errors continue to dominate with appropriate error messaging. Backend API failures show App ID resolution issues affecting 8 users. One unclassified error group suggests missing error code assignment for schema validation edge cases.

Metric	Value
Time range	last 24 hours
Total errors	165
CLI bugs	1
Backend issues	1
User errors (working as designed)	7
Unique users affected	67
Internal user occurrences	6

Errors requiring action

1. Missing error code for User schema validation — CLI bug

Error code	None (unclassified)
Occurrences	5
Users affected	5
Command	dev
Platforms	linux, darwin
PostHog	None (issue_id is null)
Existing issue	None
Recurring	No

Error: (from PostHog — the actual error message users see)

Error syncing entities: Invalid User schema: User schema cannot contain base fields: full_name. These fields are built-in and managed by the system.

Stack trace: (no stack trace captured due to missing error classification)

at runCLI (packages/cli/src/cli/index.ts:59:4)

Root cause: Entity validation error is not properly classified in the error reporting system:

// packages/cli/src/core/project/config.ts:169-175
export class SchemaValidationError extends UserError {
  readonly code = "SCHEMA_INVALID";
}

The error message indicates users have full_name field in their User entity schema, which conflicts with built-in Base44 fields. However, this specific validation error case is not being caught and properly classified with the SCHEMA_INVALID error code, resulting in null error_code and is_user_error values in telemetry.

Suggested fix: In entity schema validation code, ensure all User schema validation errors are properly wrapped with SchemaValidationError class to get correct error codes in telemetry.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
App not found (404)	15	8	entities push	link

The CLI correctly calls the entity-schemas API but receives 404 responses with "App not found" errors. This indicates app IDs in users' .app.jsonc files no longer exist in the backend, possibly due to app deletion or database changes.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
No Base44 project found	50	18	dev	link
No input provided	41	16	exec	link
Invalid entity schema	22	9	dev	link
Project already exists	13	7	eject	link
Authentication timeout	11	11	whoami	link
Deno dependency missing	4	4	exec	link
No build output directory	4	2	deploy	link

CONFIG_NOT_FOUND analysis: Users running Base44 commands outside project directories. From packages/cli/src/core/errors.ts:169-188, the CLI correctly provides hints to run base44 create or base44 link.

INVALID_INPUT analysis: Users not providing stdin input to exec command or having duplicate function names during eject. Error messaging is appropriate and working as designed.

SCHEMA_INVALID analysis: Users have invalid entity files with type mismatches or missing required fields. CLI validation correctly catches these schema violations.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
CONFIG_NOT_FOUND validation	5+ days	Referenced in #462, #459, #458, #457, #456	No dedicated issue
INVALID_INPUT validation	4+ days	Referenced in #462, #459, #458, #457	No dedicated issue
Authentication timeout	5+ days	Referenced in #462, #459, #458, #457, #456	No dedicated issue
App not found API errors	New pattern	none	no

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

INVALID_INPUT consistency: Regular pattern across multiple commands with appropriate validation messaging.

Authentication timeout pattern: 10-15 occurrences daily suggest normal OAuth service performance variability.

App not found (new): First significant occurrence of this backend API error pattern affecting 15 requests from 8 users.

Action items

1. [medium] Find and fix entity schema validation code to ensure User schema errors are properly wrapped with SchemaValidationError class for correct telemetry classification
2. [low] Backend team should investigate why 8 users are getting 404 "App not found" errors for entity-schemas endpoint - may indicate apps being deleted while users retain local configurations