Error Report: 2026-02-27 (110 errors in last 24h)

[claude]

Summary

No CLI bugs identified. The primary issues are backend deployment infrastructure problems (cron schedule validation and Deno deployment module resolution) affecting function deployments. All other errors are expected user validation patterns with stable volumes consistent with previous reports.

Metric	Value
Time range	last 24 hours
Total errors	110
CLI bugs	0
Backend issues	3
User errors (working as designed)	6
Unique users affected	68
Internal user occurrences	9

Backend issues (not CLI fixes)

Backend infrastructure issues that need server-side attention:

Error	Occurrences	Users	Command	PostHog
Invalid cron schedule expressions	12	12	functions deploy	View in error tracking
Deno deployment module resolution failures	9	9	deploy	View in error tracking
Multiple function validation errors	3	3	functions deploy	View in error tracking

Invalid cron schedule expressions (12 occurrences): Backend AWS EventBridge validation failing with "Invalid Schedule Expression cron(0 8 * * * *)" errors. The CLI correctly submits function automation schedules but AWS rejects the cron format. Backend service needs to either validate cron expressions before submission or adjust the format for EventBridge compatibility.

Deno deployment failures (9 occurrences): Functions failing to deploy due to missing module imports like "Module not found 'file:///helpers/permissionValidator.ts'" and syntax errors. These are backend Deno Deploy service issues where user code that works locally fails during remote deployment, indicating problems with the deployment environment or module resolution.

Function validation errors (9 occurrences): Backend returning HTTP 422 "Validation failed" responses during function deployment. These appear to be server-side validation issues not caught by CLI validation.

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 (0 internal)	14	link, deploy	View in error tracking
Project already exists (CONFIG_EXISTS)	10 (1 internal)	7	create, link	View in error tracking
Invalid schema files (SCHEMA_INVALID)	10 (0 internal)	6	deploy, functions deploy, eject	View in error tracking
Invalid project ID (INVALID_INPUT)	6 (0 internal)	5	link, eject	View in error tracking
Missing build output (FILE_NOT_FOUND)	5 (0 internal)	5	deploy, site deploy	View in error tracking
Missing app config (CONFIG_INVALID)	4 (0 internal)	4	deploy	View in error tracking

CONFIG_NOT_FOUND (25 occurrences) remains the highest-volume user error. The CLI correctly validates project directories and provides helpful guidance:

// src/core/project/config.ts:74-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.`,
  );
}

SCHEMA_INVALID (10 occurrences) shows users with invalid entity/function/agent definitions. The CLI provides detailed validation messages with file paths and specific error locations:

// src/core/errors.ts:226-237
constructor(context: string, zodError: z.ZodError, filePath?: string) {
  const message = filePath
    ? `${context} in ${filePath}:\n${z.prettifyError(zodError)}`
    : `${context}:\n${z.prettifyError(zodError)}`;
}

FILE_NOT_FOUND (5 occurrences) occur when users deploy 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" },
      ],
    },
  );
}

Network/Infrastructure errors

Error	Occurrences	Users	Command	PostHog
EPIPE broken pipe errors	9 (1 internal)	9	functions deploy, deploy	View in error tracking
Authentication timeouts	6 (0 internal)	6	whoami, deploy, login	View in error tracking

EPIPE errors (9 occurrences) occur during deployment operations when network connections are interrupted. The CLI correctly sets appropriate timeouts: timeout: false for functions and 180-second timeout for sites. These are network infrastructure issues, not CLI bugs.

Authentication timeouts (6 occurrences) occur within OAuth2 device code flow limits and are working as designed:

// 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.");
}

Recurring errors

Comparing with recent daily reports (issues #345, #329, #324, #312, #283):

Error	Days recurring	Existing issue	Tracked?
Function deployment timeouts/errors (API_ERROR)	8+ days	error-reports only	partially
CONFIG_NOT_FOUND (high volume)	8+ days	error-reports only	partially
SCHEMA_INVALID	8+ days	error-reports only	partially
FILE_NOT_FOUND (deploy)	8+ days	error-reports only	partially
CONFIG_EXISTS	8+ days	error-reports only	partially
Authentication timeouts	8+ days	error-reports only	partially

All major error patterns continue to recur across 8+ consecutive days with stable volumes. Function deployment issues have been consistently reported since at least issue #280, indicating persistent backend infrastructure challenges affecting Deno Deploy operations and AWS EventBridge automation setup.

The specific cron schedule validation error is new in this report compared to previous function deployment timeout patterns.

Action items

No immediate CLI fixes required. All errors fall into expected categories:

1. [low] Monitor backend cron schedule validation - new pattern of AWS EventBridge rejecting automation schedules needs backend service fixes
2. [low] Monitor Deno deployment module resolution failures - persistent backend deployment infrastructure issue affecting user workflows across 8+ consecutive days
3. [low] Consider improving FILE_NOT_FOUND error message 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, backend infrastructure issues, or network connectivity problems
• Stable recurring patterns - error types and volumes very consistent with previous 8 daily reports
• Good error handling - CLI provides clear validation messages with actionable hints for all user errors
• Backend infrastructure challenges - function deployment issues remain the primary persistent system issue, now including AWS EventBridge cron validation problems
• Low internal user ratio (9 out of 110 total errors) indicates production usage patterns rather than internal testing