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

[claude]

Summary

Backend infrastructure experiencing 502 Bad Gateway errors during secrets operations affecting 16 users. All other errors are expected user validation patterns working as designed. No CLI bugs requiring immediate action.

Metric	Value
Time range	last 24 hours
Total errors	173
CLI bugs	0
Backend issues	1
User errors (working as designed)	8
Unique users affected	99 (estimate from non-overlapping error groups)
Internal user occurrences	14

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
502 Bad Gateway on secrets API	22	16	secrets set	View
Network timeout on OAuth endpoint	3	2	login	None (issue_id null)

502 Bad Gateway analysis: The CLI correctly reports server-side infrastructure problems when the secrets API returns 502 errors. Error message shows "Request failed with status code 502 Bad Gateway: POST https://app.base44.com/api/apps/.../secrets" which is proper error propagation from backend to user.

OAuth timeout analysis: Network connectivity issues during device code flow causing "Request timed out: POST https://app.base44.com/oauth/device/code". This is infrastructure-related, not a CLI bug.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
No input provided to exec	48	22	exec	View
No Base44 project found	38	15	link	View
Authentication timed out	20	20	entities push	View
App not configured	16	8	functions list	View
Invalid app configuration schema	13	5	entities push	View
Project already linked	9	8	link	View
Deno dependency missing	4	3	exec	View
Various input validation errors	10+	14+	deploy, eject, link	Multiple PostHog links

INVALID_INPUT analysis: From the error data, users running base44 exec without piping script content get clear validation: "No input provided. Pipe a script to stdin." This is working as designed.

CONFIG_NOT_FOUND analysis: Users running commands outside Base44 project directories get appropriate guidance: "No Base44 project found. Run this command from a project directory with a config.jsonc file."

AUTH_EXPIRED analysis: From packages/cli/src/cli/utils/command/middleware.ts:10-16, when isLoggedIn() returns false, the CLI properly triggers the login flow with clear messaging: "You need to login first to continue."

SCHEMA_INVALID analysis: Configuration validation errors show specific field-level errors like "Invalid input: expected string, received undefined → at id" which provides clear guidance for fixing configuration files.

DEPENDENCY_NOT_FOUND analysis: From packages/cli/src/core/utils/dependencies.ts, the CLI properly validates Deno installation and provides installation guidance when missing.

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 #478, #476, #474, #473, #472	Yes (expected user error)
INVALID_INPUT validation	5+ days	Referenced in #478, #476, #474, #473, #472	Yes (expected user error)
AUTH_EXPIRED timeout	4+ days	Referenced in #478, #476, #474, #473	Yes (expected timeout)
502 API errors	New	None	No

The 502 Bad Gateway errors are new to today's data and represent a backend infrastructure issue affecting secrets operations.

Action items

Backend infrastructure priorities:

1. [medium] Investigate 502 Bad Gateway errors on secrets API endpoint affecting 16 users during secrets set operations - appears to be server-side infrastructure issue, not CLI

All CLI error handling is working correctly with appropriate validation messages and user guidance. No CLI code changes required.