Error Report: 2026-04-17 (330+ errors in last 24h)

[claude]

Summary

Backend deployment timeouts dominate the error landscape with 153 occurrences affecting deploy operations. Most other errors are expected user validation with appropriate CLI messaging. One critical filesystem permission issue affects user authentication setup.

Metric	Value
Time range	last 24 hours
Total errors	330+
CLI bugs	1
Backend issues	1
User errors (working as designed)	9
Unique users affected	89
Internal user occurrences	39

Errors requiring action

1. Authentication directory creation fails with permission errors — CLI bug

Error code	FILE_READ_ERROR
Occurrences	1 (0 internal)
Users affected	1
Command	login
Platforms	macOS
PostHog	None (issue_id null)
Existing issue	None
Recurring	New

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

EPERM: operation not permitted, mkdir '/Users/<redacted>/.base44/auth'
Failed to write authentication file: EPERM: operation not permitted, mkdir '/Users/<redacted>/.base44/auth'

Stack trace: (only CLI stack trace frames)

at runCLI (packages/cli/src/cli/index.ts:59:4)
at Command.parseAsync (commander/lib/command.js:1243:4)

Root cause: The CLI attempts to create the authentication directory without handling filesystem permission errors gracefully:

// packages/cli/src/core/utils/fs.ts:111
await mkdir(dir, { recursive: true });

When called from writeAuth() in packages/cli/src/core/auth/config.ts:63 via writeJsonFile(getAuthFilePath(), result.data), this tries to create ~/.base44/auth/ but fails when the user's system restricts directory creation in the home folder.

Suggested fix: In packages/cli/src/core/utils/fs.ts:111, wrap the mkdir call in a try-catch block to handle EPERM errors gracefully and throw a more helpful FileReadError with clear guidance about filesystem permissions and alternative auth storage options.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Deployment API timeouts	153	19	deploy, site deploy	View
Auth token exchange timeouts	4	3	exec	View
Connector listing timeouts	6	4	deploy	View
Secret deletion 404 errors	3	1	secrets delete	View
Entity sync for non-Backend Platform apps	3	2	deploy	View
OAuth expired token	3	1	whoami	View

Deployment timeout analysis: The CLI correctly configures a 3-minute timeout for deployment operations (packages/cli/src/core/site/api.ts:26), but the backend deployment API is exceeding this limit. Error messages show "Request timed out: POST https://app.base44.com/api/apps/.../deploy-dist" which indicates backend infrastructure performance issues, not CLI problems.

Backend Platform restriction analysis: The CLI correctly reports 428 Precondition Required when users try to access Backend Platform features with incompatible app types. The error message "This endpoint is only available for Backend Platform apps" provides appropriate guidance.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Project not found validation	66	41	link, dev, deploy	View
Link command validation errors	50	19	link	View
Authentication timeout	14	14	whoami, deploy	View
Entity schema validation errors	8	6	eject	View
Project already linked	7	5	link	View
Deno dependency missing	4	4	exec	View
SSO configuration validation	13	8	auth sso	Multiple PostHog links
Non-interactive mode validation	14	18	link, deploy	Multiple PostHog links
App configuration errors	5	3	deploy, functions deploy	Multiple PostHog links

CONFIG_NOT_FOUND analysis: From packages/cli/src/core/project/config.ts:75, 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."

INVALID_INPUT analysis: Various validation patterns including link command flags ("--create with --name, or --projectId, is required in non-interactive mode"), duplicate function names, missing required SSO parameters, and non-interactive mode requirements all provide appropriate error messaging.

SCHEMA_INVALID analysis: Entity validation errors show specific field-level guidance like "Field condition values must be a primitive or an operator object ($in, $nin, $ne, $all) → at rls.create.$or[2]" which helps users fix their entity files.

AUTH_EXPIRED analysis: Authentication timeout handling provides clear guidance with "Authentication timed out. Please try again." from packages/cli/src/core/errors.ts:150.

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: From packages/cli/src/core/utils/dependencies.ts, the CLI validates Deno installation and provides clear guidance when missing for script execution.

Environment issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Path corruption on Windows	1	1	eject	View

Path corruption analysis: Error shows "File not found: /Users/macbook/lumina-data-base/Users/macbook/Desktop/Resita/ Data_test/base44/config.jsonc" where paths are incorrectly concatenated. This appears to be an environment-specific path resolution issue rather than a systematic CLI bug.

Recurring errors

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

Error	Days recurring	Existing issue	Tracked?
Deployment API timeouts	5+ days	Referenced in #483, #479, #478, #476, #474	Yes (backend issue)
CONFIG_NOT_FOUND validation	6+ days	Referenced in #483, #479, #478, #476, #474	Yes (expected user error)
INVALID_INPUT validation	6+ days	Referenced in #483, #479, #478, #476, #474	Yes (expected user error)
Authentication timeout	5+ days	Referenced in #483, #479, #478, #476, #474	Yes (expected timeout)
Schema validation errors	5+ days	Referenced in #483, #479, #478, #476, #474	Yes (expected user error)

The deployment timeout issue is the only significant recurring technical problem and represents a backend infrastructure concern requiring server-side investigation.

Action items

1. [medium] packages/cli/src/core/utils/fs.ts:111 — Add try-catch around mkdir call to handle EPERM errors gracefully with clear error messaging about filesystem permissions and potential alternative auth storage locations

Backend infrastructure priorities require server-side attention:

2. [high] Investigate deployment API timeout issues affecting 153 occurrences across 19 users during site deployment operations — backend performance optimization needed

3. [low] Review 3-minute deployment timeout configuration in packages/cli/src/core/site/api.ts:26 — consider increasing timeout or implementing progress feedback for long deployments

All user validation errors show appropriate CLI behavior with clear error messages and actionable guidance. No additional CLI code changes required for user error patterns.