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

[claude]

Summary

User validation errors dominate with expected behavior and clear CLI messaging. Backend API restrictions for non-Backend Platform apps generate moderate error volume. One environment issue shows disk space failures during project setup. No critical CLI bugs identified.

Metric	Value
Time range	last 24 hours
Total errors	207
CLI bugs	0
Backend issues	3
User errors (working as designed)	7
Unique users affected	83
Internal user occurrences	36

Errors requiring action

No CLI bugs requiring immediate action. All errors are either backend issues or working as designed user validation errors.

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Backend Platform app requirement (428)	33	15	deploy, site deploy, entities push	View
App not found (404) for token exchange	3	2	exec	View
Functions quota exceeded (422)	3	1	functions deploy	View
OAuth expired token (400)	2	1	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, function deployment) with incompatible app types. Server returns clear error messages like "This endpoint is only available for Backend Platform apps".

Functions quota analysis: API returns 422 Unprocessable Entity with "Too many functions. Maximum is 50, got 51" which the CLI correctly passes through with proper error context.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Function not found validation	52	16	logs	View
No Base44 project found	40	15	dev, deploy, link	View
Authentication timeout	15	15	whoami, deploy, login	View
Invalid app configuration	11	6	functions deploy, deploy	View
App not configured	11	6	functions deploy	View
Various input validation errors	41	19	deploy, eject, link, exec	Multiple PostHog links
Project already exists	9	6	eject, link	View
Deno dependency missing	7	5	dev	View
Output directory doesn't exist	2	2	site deploy	View

Function validation analysis: From packages/cli/src/cli/commands/project/logs.ts:127, when API returns 404 for non-existent functions like "seed-people", CLI throws InvalidInputError with helpful hints showing available functions and deployment guidance.

CONFIG_NOT_FOUND analysis: From packages/cli/src/core/project/app-config.ts:49, when findProjectRoot() returns null (no config.jsonc found), CLI throws clear error with guidance to run commands from Base44 project directories.

Deno dependency analysis: From packages/cli/src/core/utils/dependencies.ts:7, CLI validates Deno installation via spawn('deno', ['--version']) and provides installation link when missing for backend function execution.

Schema validation analysis: Configuration files with missing required fields (e.g., missing 'id' or 'entry' properties) trigger proper Zod validation with field-specific error messages.

Environment issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Disk space exhausted (ENOSPC)	7	6	eject	None (issue_id null)
Git permission errors (EPERM)	3	2	deploy	View

ENOSPC analysis: From packages/cli/src/cli/commands/project/eject.ts:164, CLI runs npm install via execa in project directory. When user's machine is out of disk space, npm fails with "TAR_ENTRY_ERROR ENOSPC: no space left on device" which CLI correctly reports as command failure.

EPERM analysis: Git worktree scandir operations fail on Windows when accessing restricted directories. CLI correctly surfaces these filesystem permission errors.

Recurring errors

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

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

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 (33 occurrences) are working as designed but may benefit from clearer documentation about app type differences

2. [info] Function validation errors (52 occurrences) provide appropriate guidance but suggest users need better understanding of function deployment workflow

3. [info] Config validation errors (51 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.