Error Report: 2026-02-23 (116 errors in last 24h)

[claude]

Summary

No critical CLI bugs identified. Most errors are backend infrastructure issues (function deployment timeouts) or expected user validation errors. The authentication timeout error uses a generic Error type but is working as designed within OAuth2 device code flow limits.

Metric	Value
Time range	last 24 hours
Total errors	116
CLI bugs	0
Backend issues	3
User errors (working as designed)	5
Unique users affected	47
Internal user occurrences	16

Backend issues (not CLI fixes)

Backend infrastructure issues that need server-side attention:

Error	Occurrences	Users	Command	PostHog
Function deployment timeouts	29	13	functions deploy	View in error tracking
Backend Platform feature restrictions	5	5	functions deploy	View in error tracking
Site deployment timeouts	4	4	deploy	View in error tracking

Function deployment timeouts (29 occurrences): Deno deployment operations consistently timing out after 90 seconds with messages like "Operation wait_for_deployment(dupr-lookup) timed out after 90 seconds". The CLI correctly handles this by setting timeout: false in the HTTP client and reporting server-side timeout messages.

Stack trace: (from PostHog)

at runCLI (src/cli/index.ts:33:4)

Root cause: Backend deployment infrastructure taking longer than 90-second server timeout:

// src/core/resources/function/api.ts:34-36
response = await appClient.put("backend-functions", {
  json: payload,
  timeout: false, // No client timeout - correctly defers to server
});

Backend Platform restrictions (5 occurrences): HTTP 428 responses with "This endpoint is only available for Backend Platform apps" when users try to deploy functions to non-Backend Platform apps. Working as designed but suggests user confusion about app platform types.

Site deployment timeouts (4 occurrences): HTTP timeouts during site deployment POST requests. Backend infrastructure issue affecting site upload operations.

User errors (working as designed)

Expected user errors where CLI validation is correct:

Error	Occurrences	Users	Command	PostHog
No project found (CONFIG_NOT_FOUND)	25	9	link	View in error tracking
Project already linked (CONFIG_EXISTS)	16	9	eject	View in error tracking
Authentication timeout	11	9	create	No PostHog link available
Invalid entity schemas (SCHEMA_INVALID)	10	6	deploy	View in error tracking
Missing build output (FILE_NOT_FOUND)	9	4	site deploy	View in error tracking

CONFIG_NOT_FOUND errors (25 occurrences) are the highest volume user error. The CLI correctly validates project directories:

// src/core/project/config.ts:73-76
if (!found) {
  throw new ConfigNotFoundError(
    `Project root not found. Please ensure config.jsonc or config.json exists in the project directory or ${PROJECT_SUBDIR}/ subdirectory.`,
  );
}

Authentication timeouts (11 occurrences) occur within OAuth2 device code flow limits. The CLI correctly handles this with clear messaging:

// src/cli/commands/auth/login-flow.ts:70-72
if (error instanceof Error && error.message.includes("timed out")) {
  throw new Error("Authentication timed out. Please try again.");
}

SCHEMA_INVALID errors (10 occurrences) show users with invalid entity definitions. The CLI provides detailed validation messages with file paths and specific error locations.

FILE_NOT_FOUND errors (9 occurrences) occur when users deploy sites without building first. The CLI correctly validates output directories and provides helpful hints:

// src/core/site/deploy.ts:14-22
if (!(await pathExists(siteOutputDir))) {
  throw new FileNotFoundError(
    `Output directory does not exist: ${siteOutputDir}. Make sure to build your project first.`,
    {
      hints: [
        { message: "Run your build command (e.g., 'npm run build') first" },
      ],
    },
  );
}

Recurring errors

Comparing with recent daily reports (issues #280, #281, #283):

Error	Days recurring	Existing issue	Tracked?
Function deployment timeouts	4+ days	error-reports only	partially
CONFIG_NOT_FOUND (high volume)	4+ days	error-reports only	partially
Authentication timeouts	4+ days	error-reports only	partially
FILE_NOT_FOUND (site deploy)	4+ days	error-reports only	partially
SCHEMA_INVALID	3+ days	error-reports only	partially

All major error patterns continue to recur across multiple days. Function deployment timeout issues have been consistently reported since at least issue #272 (4+ days ago), indicating persistent backend infrastructure challenges.

Additional errors

Lower-volume errors worth noting:

• INVALID_INPUT (7 occurrences): Users providing invalid project IDs during linking - working as designed
• CONFIG_INVALID (5 occurrences): Missing .app.jsonc files - working as designed
• ExecaError during eject (4 occurrences): Build failures during project ejection, likely due to missing entity files after scaffolding
• File permission errors during create (1 occurrence): Windows permission issues during template processing

Action items

1. [low] Monitor function deployment timeout patterns - this is a backend infrastructure issue consistently affecting user workflows across multiple days
2. [low] Monitor Backend Platform availability error messaging to determine if UX improvements are needed to clarify app platform types
3. [low] Consider improving FILE_NOT_FOUND error messages to detect common build commands from package.json and suggest specific build steps

Notes

• Zero CLI bugs identified - all errors are either working as designed user validation or backend infrastructure issues
• Stable recurring patterns - error types and volumes consistent with previous daily reports
• Good error handling - CLI provides clear validation messages with actionable hints for user errors
• Backend infrastructure challenges - function deployment timeouts remain the primary system issue affecting user experience