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

[claude]

Summary

User validation errors continue at expected levels with appropriate CLI messaging. Backend API restrictions and JSON parsing issues affect some users. One potential CLI bug with malformed JSON response parsing needs investigation.

Metric	Value
Time range	last 24 hours
Total errors	181
CLI bugs	1
Backend issues	2
User errors (working as designed)	6
Unique users affected	71+
Internal user occurrences	12

Errors requiring action

1. JSON response parsing error — CLI bug

Error code	null
Occurrences	6 (0 internal)
Users affected	4
Command	deploy
Platforms	Multiple
PostHog	None (no issue_id)
Existing issue	None
Recurring	No

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

SyntaxError: Unexpected token 'H', "Host resol"... is not valid JSON

Stack trace: (insufficient stack trace data in PostHog)

at JSON.parse (during deploy operation)

Root cause: JSON response parsing failure during deploy command. The error suggests a malformed response starting with "Host resol" which indicates the API may be returning non-JSON content (possibly HTML error pages or redirects) that the CLI attempts to parse as JSON.

// packages/cli/src/core/errors.ts:344-355
try {
  responseBody = await error.response.clone().json();
  const parsed = ApiErrorResponseSchema.safeParse(responseBody);
  // ... error formatting
} catch {
  message = error.message;
}

Suggested fix: In packages/cli/src/core/errors.ts:344, add content-type validation before attempting JSON parsing to handle non-JSON responses gracefully and provide clearer error messages when the API returns unexpected content types.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Backend Platform app restrictions (428)	11	9+	deploy, entities push	View
OAuth token expiration (400)	2	2	functions list	View

Backend Platform restrictions represent server-side business rules where users attempt operations not available for their app type. OAuth expiration errors indicate backend authentication service issues.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Project not found validation	60	21	exec, link	View
Duplicate function names	47	21	eject	View
Project already linked	10	5	link	View
App configuration missing	9	7	secrets list, functions deploy	View
Deno dependency missing	8	6	exec	View
Authentication timeout	6	6	deploy	View

All user errors provide appropriate validation messages and actionable guidance. CLI error handling is working correctly across all validation categories.

Environment issues

Error	Occurrences	Users	Command	PostHog
Build tool missing during create	3	3	create	View
Output directory missing	4	4	deploy	View

Environment issues where users lack required build tools (vite) or haven't run build commands before deployment.

Recurring errors

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

Error	Days recurring	Existing issue	Tracked?
CONFIG_NOT_FOUND validation	11+ days	Referenced in #493, #492, #490, #489, #488	Yes (expected user error)
INVALID_INPUT validation	11+ days	Referenced in #493, #492, #490, #489, #488	Yes (expected user error)
Backend Platform restrictions	4+ days	Referenced in #493, #492, #490	Yes (backend business rules)
Authentication timeout	11+ days	Referenced in #493, #492, #490, #489, #488	Yes (expected timeout)
Dependency validation	11+ days	Referenced in #493, #492, #490, #489, #488	Yes (expected user error)

The JSON parsing error is new and represents the only CLI bug requiring investigation. All other patterns are expected user validation or documented backend behaviors.

Action items

1. [medium] packages/cli/src/core/errors.ts:344 — Add content-type validation before JSON parsing to handle non-JSON API responses gracefully and provide clearer error messages when backend returns HTML error pages or redirects