Summary
User input validation errors dominate with 117 INVALID_INPUT occurrences, primarily from eject command encountering non-existent project IDs. API timeout issues affect 21 occurrences when setting secrets, indicating potential backend infrastructure problems. Configuration errors are working as designed but may indicate UX gaps.
| Metric |
Value |
| Time range |
last 24 hours |
| Total errors |
234 |
| CLI bugs |
0 |
| Backend issues |
2 |
| User errors (working as designed) |
6 |
| Unique users affected |
55 |
| Internal user occurrences |
93 |
Backend issues (not CLI fixes)
| Error |
Occurrences |
Users |
Command |
PostHog |
| API timeout setting secrets |
21 |
8 |
secrets set |
link |
| Authentication timeout |
10 |
9 |
login |
link |
API Timeout Analysis: The secrets API call has timeout: false configured in /packages/cli/src/core/resources/secret/api.ts:46, suggesting this is a backend performance issue rather than a client timeout setting. The error "Request timed out: POST https://app.base44.com/api/apps//secrets" indicates server-side processing delays.
Authentication Timeout: Login flow timeouts with "Authentication timed out. Please try again." suggest OAuth provider or authentication service delays.
User errors (working as designed)
| Error |
Occurrences |
Users |
Command |
PostHog |
| Project not found for eject |
74 |
19 |
eject |
link |
| Config not found in directory |
36 |
17 |
deploy/link |
link |
| App not configured |
14 |
6 |
functions deploy |
link |
| Invalid app configuration |
15 |
5 |
dev |
link |
| Deno dependency missing |
13 |
3 |
dev/exec |
link |
| Missing required parameters |
9 |
8 |
link |
link |
High-volume pattern: The "Project not found for eject" error (74 occurrences) suggests users are frequently trying to eject non-existent or inaccessible projects. This could indicate:
- Project IDs becoming stale in user workflows
- Insufficient error messaging when project access is revoked
- Potential UX improvement: better error message suggesting
base44 projects list to find valid project IDs
Config errors: CONFIG_NOT_FOUND and CONFIG_INVALID are working as designed - users running commands outside Base44 projects or with missing .app.jsonc files.
Recurring errors
Based on error patterns from previous reports (#451), similar validation and configuration errors continue to appear daily, indicating consistent user behavior patterns rather than new bugs.
| Error |
Days recurring |
Existing issue |
Tracked? |
| INVALID_INPUT validation |
2+ days |
#451 |
yes |
| CONFIG_NOT_FOUND |
2+ days |
#451 |
yes |
| API timeouts |
New pattern |
none |
no |
New concerning pattern: API timeout errors for secrets endpoint are a new pattern not seen in previous reports, suggesting recent backend performance degradation.
Action items
- [high] Investigate backend performance for secrets API endpoint - 21 timeouts despite disabled client timeout configuration
- [medium] Monitor authentication service performance - 10 login timeouts affecting 9 users
- [low] Consider UX improvement for eject command error messaging when project ID not found (74 occurrences suggests common user confusion)
Summary
User input validation errors dominate with 117 INVALID_INPUT occurrences, primarily from
ejectcommand encountering non-existent project IDs. API timeout issues affect 21 occurrences when setting secrets, indicating potential backend infrastructure problems. Configuration errors are working as designed but may indicate UX gaps.Backend issues (not CLI fixes)
secrets setloginAPI Timeout Analysis: The secrets API call has
timeout: falseconfigured in/packages/cli/src/core/resources/secret/api.ts:46, suggesting this is a backend performance issue rather than a client timeout setting. The error "Request timed out: POST https://app.base44.com/api/apps//secrets" indicates server-side processing delays.Authentication Timeout: Login flow timeouts with "Authentication timed out. Please try again." suggest OAuth provider or authentication service delays.
User errors (working as designed)
ejectdeploy/linkfunctions deploydevdev/execlinkHigh-volume pattern: The "Project not found for eject" error (74 occurrences) suggests users are frequently trying to eject non-existent or inaccessible projects. This could indicate:
base44 projects listto find valid project IDsConfig errors: CONFIG_NOT_FOUND and CONFIG_INVALID are working as designed - users running commands outside Base44 projects or with missing
.app.jsoncfiles.Recurring errors
Based on error patterns from previous reports (#451), similar validation and configuration errors continue to appear daily, indicating consistent user behavior patterns rather than new bugs.
New concerning pattern: API timeout errors for secrets endpoint are a new pattern not seen in previous reports, suggesting recent backend performance degradation.
Action items