Error Report: 2026-02-18 (145 errors in last 24h)

[claude]

System analysis reveals three critical bugs: AWS cron validation blocking function deployments (39 occurrences, 19 users), Windows path concatenation bug in eject command (19 occurrences, 18 users), and misleading error classification for missing build directories (13 occurrences, 10 users).

Key Metrics

• Time range: last 24 hours
• Total errors: 145
• System errors: 71
• User errors (noteworthy): 16
• Unique users affected: ~65
• Internal users affected: 1

Critical Issues

Issue 1: AWS Cron Expression Validation Bug - API_ERROR (39 occurrences, 19 users)
Function deployments fail when backend sends malformed cron expressions to AWS EventBridge Scheduler. Error: 'Invalid Schedule Expression cron(0 7 * * * *)'.

Root cause: CLI validates cron expressions with basic Zod schema but backend likely formats them incorrectly for AWS API.

Location: src/core/resources/function/schema.ts:36-38

Issue 2: Windows Path Concatenation Bug - null error code (19 occurrences, 18 users)
Eject command fails on Windows with malformed paths like 'C:\WINDOWS\System32\project-namecd C:\Users\user'.

Root cause: Path resolution issue causing current directory to be incorrectly concatenated with target path.

Location: src/cli/commands/project/eject.ts:99, src/core/utils/fs.ts:129-133

Issue 3: Misleading Error Classification - FILE_NOT_FOUND (13 occurrences, 10 users)
Deploy command without build shows as system error instead of user error, inflating bug metrics.

Root cause: FileNotFoundError for missing dist directory should be user error classification.

Location: src/core/site/deploy.ts:14-22

Suggestions

1. Critical: Fix AWS cron validation or backend formatting
2. High: Resolve Windows path concatenation in eject command
3. Medium: Reclassify missing build directory as user error
4. Low: Add project creation validation for empty app names