This page covers what to do when something goes wrong in your project, whether during local development or in production.
When working with the CLI, it will give you detailed error messages with actionable hints directly in your terminal.
Check the status page
Visit the Base44 status page before debugging further. If there’s a platform-wide incident, your issue may resolve on its own.
Local dev tokens don’t work in production
If you register or log in during local development and then switch to your deployed app, you may see authentication errors even though everything worked locally. The local dev server signs tokens with a local secret. Your deployed app uses a different secret, so it rejects local tokens.
To fix the issue, sign out of your local session or delete your tokens from your local browser storage and then log in through your deployed app. The deployed app issues a new, valid production token.
Debug backend functions
If you’re using an AI coding agent, the base44-troubleshooter skill teaches it to fetch and analyze your backend function logs automatically. Ask your agent something like “show me all errors from the last hour” and it will pull the relevant logs, identify patterns, and suggest fixes.
For manual debugging, use the logs command to view function output, errors, and timing information. You can filter by function name, log level, and time range.
Get help
Ask questions, share feedback, and request features on GitHub Discussions. 
