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

[claude]

Summary

User validation errors dominate with appropriate CLI messaging. Backend API agent sync issues affect some users. One minor path construction issue during eject operations. All CLI error handling working correctly with clear user guidance.

Metric	Value
Time range	last 24 hours
Total errors	161
CLI bugs	0
Backend issues	2
User errors (working as designed)	7
Unique users affected	69
Internal user occurrences	32

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
Agent sync function validation (400)	11	11	agents push, deploy	View
Backend Platform restrictions (428)	16	14	deploy, entities push	View

Agent sync validation analysis: The CLI correctly makes PUT requests to the backend agent-configs endpoint via pushAgents() in packages/cli/src/core/resources/agent/api.ts:25. The backend returns 400 Bad Request with messages like "Function tool references non-existent function 'rtv_validator'" when agents reference functions that don't exist. The CLI properly reports these via ApiError.fromHttpError() at line 30. This is working backend validation logic, not a CLI issue.

Backend Platform restrictions analysis: Backend returns 428 Precondition Required with messages like "This endpoint is only available for Backend Platform apps" when users try to access features unavailable for their app type. The CLI properly reports these via the same ApiError.fromHttpError() mechanism.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Non-interactive mode validation	46	18	link	View
Project not found validation	45	19	link, exec	View
App configuration missing	14	7	functions pull, deploy	View
Authentication timeout	13	13	whoami, login	View
Function config validation	11	6	eject	View
Project already linked	7	5	link	View
Deno dependency missing	3	3	exec	View

INVALID_INPUT analysis: From packages/cli/src/cli/commands/project/link.ts:136-138, the CLI properly validates non-interactive mode requirements with clear messaging: "--create with --name, or --projectId, is required in non-interactive mode". This provides appropriate guidance for CI/CD environments.

CONFIG_NOT_FOUND analysis: From packages/cli/src/core/project/app-config.ts and link.ts:144-146, when findProjectRoot() returns null (no config.jsonc found), the CLI throws clear guidance: "No Base44 project found. Run this command from a project directory with a config.jsonc file." This is working as designed.

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.

AUTH_EXPIRED analysis: Authentication timeout handling provides clear guidance with "Authentication timed out. Please try again." directing users to re-authenticate.

SCHEMA_INVALID analysis: Function configuration validation from Zod provides specific field-level guidance like "Invalid function configuration in /function.jsonc: ✖ Invalid input → at automations[0]" which helps users fix their configuration files.

CONFIG_EXISTS analysis: 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: 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
Path construction edge case	2	1	eject	View

Path duplication analysis: Single occurrence showing "ENOENT: no such file or directory, mkdir 'C:\\Users\\User\\Documents\\finance\\C:\\Users\\User\\Documents\\finance'" with duplicated path segments. The eject command uses resolve() from Node.js path module at packages/cli/src/cli/commands/project/eject.ts:114 and makeDirectory() at packages/cli/src/core/utils/fs.ts:129 which both use standard Node.js APIs. The path duplication suggests an edge case in user input or environment, but very low impact (1 user, 2 occurrences).

Recurring errors

Based on previous daily reports (issues #494, #493, #492, #490, #489), these errors continue from multiple days:

Error	Days recurring	Existing issue	Tracked?
CONFIG_NOT_FOUND validation	12+ days	Referenced in #494, #493, #492, #490, #489	Yes (expected user error)
INVALID_INPUT validation	12+ days	Referenced in #494, #493, #492, #490, #489	Yes (expected user error)
Backend Platform restrictions (428)	5+ days	Referenced in #494, #493, #492, #490	Yes (backend business rules)
Agent sync errors (400)	New	None	No
Authentication timeout	12+ days	Referenced in #494, #493, #492, #490, #489	Yes (expected timeout)
Dependency validation	12+ days	Referenced in #494, #493, #492, #490, #489	Yes (expected user error)
Configuration validation errors	12+ days	Referenced in #494, #493, #492, #490, #489	Yes (expected user error)

The agent sync function reference errors are new to today's data and represent backend validation of agent configurations that reference non-existent functions.

Action items

No CLI code changes required. Backend validation and business rules are working as designed:

1. [low] Agent sync function validation (400 errors) represent backend validation where agents reference functions that don't exist - users receive appropriate error messages via the CLI's standard API error handling
2. [low] Backend Platform app restrictions (428 errors) represent backend access control - users attempting to use features unavailable for their app type receive appropriate error messages