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

[claude]

Summary

File size handling bug affects users deploying large sites. Backend Platform app requirement errors continue at high volume. User validation errors are working as designed with appropriate messaging.

Metric	Value
Time range	last 24 hours
Total errors	237
CLI bugs	2
Backend issues	2
User errors (working as designed)	6
Unique users affected	63
Internal user occurrences	5

Errors requiring action

1. File size limit exceeded in site deployment — CLI bug

Error code	FILE_READ_ERROR
Occurrences	1 (0 internal)
Users affected	1
Command	deploy
Platforms	Unknown
PostHog	None (issue_id is null)
Existing issue	None
Recurring	No

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

Failed to read file /var/folders/2q/b0sdx_dn46x3xmdtkkq5wg180000gn/T/base44-site-e6d9cd23-bfce-4f25-94b0-a288ba62d7c2.tar.gz: File size (14976034628) is greater than 2 GiB

Stack trace: (no CLI stack trace captured due to unclassified error)

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

Root cause: Node.js has a built-in 2 GiB limit for file operations, but the CLI doesn't validate archive size before attempting to read:

// packages/cli/src/core/utils/fs.ts:46-61
export async function readFile(filePath: string): Promise<Buffer> {
  if (!(await pathExists(filePath))) {
    throw new FileNotFoundError(`File not found: ${filePath}`);
  }

  try {
    return await fsReadFile(filePath); // <-- Fails on files > 2 GiB
  } catch (error) {
    throw new FileReadError(
      `Failed to read file ${filePath}: ${
        error instanceof Error ? error.message : "Unknown error"
      }`,
      { cause: error instanceof Error ? error : undefined },
    );
  }
}

Suggested fix: In packages/cli/src/core/site/deploy.ts:42, add file size validation after creating the archive and before uploading to provide a better error message for oversized deployments.

2. Unhandled EPIPE errors in CLI execution — needs investigation

Error code	None (unclassified)
Occurrences	5 (0 internal)
Users affected	5
Command	whoami
Platforms	Unknown
PostHog	None (no error classification)
Existing issue	None
Recurring	No

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

write EPIPE

Stack trace: (no CLI stack trace captured due to unclassified error)

(Stack trace not available)

Root cause: EPIPE (Broken pipe) errors typically occur when writing to a closed pipe or process. This suggests potential issues with process handling or parent process termination during CLI execution.

Suggested fix: Add proper error handling for EPIPE errors in the CLI error handler and investigate process lifecycle management for commands like whoami.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Backend Platform app requirement	17	10	deploy, entities push	View
API timeout during token exchange	6	5	exec	View
OAuth expired token	2	2	whoami	View
App not found (404)	2	1	functions pull	View

These are not CLI bugs but may need backend team attention. The Backend Platform app errors continue to be the largest backend issue.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
No Base44 project found	60	19	link, logs	View
Invalid project/function configuration	37	23	eject, functions deploy	View
Entity schema validation errors	28	8	entities push, connectors pull	View
Authentication timeout	16	15	whoami, login	View
App configuration missing	12	10	deploy, dashboard open	View
Deno dependency missing	12	4	exec	View
Build directory missing	7	5	deploy, site deploy	View
Project already linked/exists	8	5	link, eject	View

All user error volumes are within expected ranges. The CLI is correctly validating and providing appropriate error messages.

Recurring errors

Based on previous daily reports, these errors have appeared multiple days:

Error	Days recurring	Existing issue	Tracked?
Backend Platform app requirement	4+ days	None	No
No Base44 project found	4+ days	None	No (expected user error)
Authentication timeout	4+ days	None	No (expected user error)

The Backend Platform app requirement error is an untracked recurring backend issue affecting multiple users daily.

Action items

1. [high] packages/cli/src/core/site/deploy.ts:42 — Add file size validation after tar creation and before upload attempt to prevent Node.js 2 GiB limit errors with better messaging
2. [medium] Investigate EPIPE error handling — Add specific error handling for broken pipe errors and review process lifecycle management
3. [low] Backend Platform app requirement — This recurring error may need better error messaging or documentation to reduce user confusion