Base44 not working?
Here's what to check first, and when to get help.
Common issues and what to check
Publish fails or nothing happens
You click publish and either get an error or the publish seems to succeed but your changes don't appear.
Check first:
- •Look at the build logs. Base44 usually shows them after a publish attempt.
- •Make sure all required environment variables are set in your production environment.
- •Clear your browser cache or open an incognito window to rule out caching.
- •Check if your app is using the correct environment (prod vs. preview).
If none of that helps, there's likely an issue with your build process or schema validation.
Data not showing up
Your entities exist in Base44 but the data doesn't appear in your app.
Check first:
- •Verify your query is targeting the right entity and fields.
- •Look for field name mismatches between your schema and your query.
- •Check if there are any filters or conditions that might be excluding the data.
- •Make sure the data actually exists in the environment you're viewing (prod vs. dev).
Entity schema mismatches are one of the most common Base44 issues. The generated schema might not match your actual data structure.
Connectors failing
Your OAuth connector, API integration, or webhook isn't working.
Check first:
- •Make sure your API credentials are correct and haven't expired.
- •Check that your OAuth redirect URLs match what's registered with the provider.
- •Look for rate limiting or quota errors in the connector logs.
- •Verify the connector has the necessary permissions or scopes.
Connector errors are often cryptic. If the logs don't point to an obvious fix, it's worth having someone look at the full configuration.
App works in preview but not production
Everything looks fine in preview mode, but production is broken or behaves differently.
Check first:
- •Environment variables: preview and production often have different values.
- •Asset paths: some paths work in preview but fail after deployment.
- •Caching: production might be serving cached versions of your app or API responses.
- •Database or data environment: make sure production is pointing to the right data source.
This kind of issue usually comes down to configuration differences between environments.
When to get help
If you've checked the obvious things and it's still not working, don't spend days guessing. Most Base44 issues follow predictable patterns once you know what to look for.
We've debugged enough Base44 apps to recognize these patterns quickly. If you're stuck, tell us what's happening and we'll take a look.