Summary
No CLI bugs identified. All errors are either expected user validation errors with appropriate messaging or backend API restrictions. The majority are users running commands in wrong contexts or with missing dependencies.
| Metric |
Value |
| Time range |
last 24 hours |
| Total errors |
236 |
| CLI bugs |
0 |
| Backend issues |
3 |
| User errors (working as designed) |
7 |
| Unique users affected |
105 |
| Internal user occurrences |
8 |
Backend issues (not CLI fixes)
Brief table of errors caused by the backend/server, not the CLI:
| Error |
Occurrences |
Users |
Command |
PostHog |
| 428 Precondition Required - Backend Platform restriction |
25 |
25 |
deploy, entities push |
link |
| 404 App not found - token exchange |
6 |
6 |
exec |
link |
| 400 OAuth expired_token |
3 |
3 |
whoami |
link |
These are server-side restrictions and authentication issues, not CLI problems.
User errors (working as designed)
Brief table of expected user errors where the CLI validation is correct:
| Error |
Occurrences |
Users |
Command |
PostHog |
| Function entry file not found |
95 |
21 |
eject |
link |
| Non-interactive mode requires --project-id |
31 |
17 |
eject, link |
link |
| No Base44 project found |
29 |
11 |
logs, link |
link |
| Authentication timeout |
16 |
16 |
exec, login |
link |
| Deno dependency missing |
14 |
8 |
exec, dev |
link |
| Invalid entity/config schemas |
20 |
8 |
functions deploy, entities push, deploy |
Multiple |
| Project already linked |
11 |
12 |
link |
link |
All validation messages are appropriate with helpful hints for resolution.
Recurring errors
Based on previous error reports, the Backend Platform 428 errors and function validation errors continue to appear consistently. These are expected patterns:
| Error |
Days recurring |
Existing issue |
Tracked? |
| Backend Platform API restriction |
5+ days |
Multiple error reports |
Yes, in daily reports |
| Function validation errors |
5+ days |
Multiple error reports |
Yes, in daily reports |
Action items
No action items required - all errors are working as designed with appropriate messaging or are backend issues outside CLI scope.
Technical analysis
Function entry file not found (95 occurrences): Users have function configs that reference missing entry files. Code analysis shows proper validation:
// packages/cli/src/core/resources/function/config.ts:40-47
if (!(await pathExists(entryPath))) {
throw new InvalidInputError(
`Function entry file not found: ${entryPath} (referenced in ${configPath})`,
{
hints: [{ message: "Check the 'entry' field in your function config" }],
},
);
}
Non-interactive mode validation (31 occurrences): Agents/CI running commands without required flags. Working as designed:
// packages/cli/src/cli/commands/project/eject.ts:36-40
if (isNonInteractive && !options.projectId) {
throw new InvalidInputError(
"--project-id is required in non-interactive mode",
);
}
Deno dependency checks (14 occurrences): Users trying to run functions without Deno installed. Proper detection and helpful error:
// packages/cli/src/core/utils/dependencies.ts:4-16
export function verifyDenoInstalled(context: string): void {
const result = spawnSync("deno", ["--version"]);
if (result.error) {
throw new DependencyNotFoundError(`Deno is required ${context}`, {
hints: [{
message: "Install Deno: https://docs.deno.com/runtime/getting_started/installation/",
}],
});
}
}
All errors show appropriate validation with helpful messaging for user resolution.
Summary
No CLI bugs identified. All errors are either expected user validation errors with appropriate messaging or backend API restrictions. The majority are users running commands in wrong contexts or with missing dependencies.
Backend issues (not CLI fixes)
Brief table of errors caused by the backend/server, not the CLI:
deploy,entities pushexecwhoamiThese are server-side restrictions and authentication issues, not CLI problems.
User errors (working as designed)
Brief table of expected user errors where the CLI validation is correct:
ejecteject,linklogs,linkexec,loginexec,devfunctions deploy,entities push,deploylinkAll validation messages are appropriate with helpful hints for resolution.
Recurring errors
Based on previous error reports, the Backend Platform 428 errors and function validation errors continue to appear consistently. These are expected patterns:
Action items
No action items required - all errors are working as designed with appropriate messaging or are backend issues outside CLI scope.
Technical analysis
Function entry file not found (95 occurrences): Users have function configs that reference missing entry files. Code analysis shows proper validation:
Non-interactive mode validation (31 occurrences): Agents/CI running commands without required flags. Working as designed:
Deno dependency checks (14 occurrences): Users trying to run functions without Deno installed. Proper detection and helpful error:
All errors show appropriate validation with helpful messaging for user resolution.