You can fix this yourself. Revert, redeploy or clone inside Base44.
- How serious
- Medium
- Fix it yourself?
- Yes, you can fix this yourself
- Typical cost
- $49–$800 one-off check if it persists (prices)
- Top rated for Base44
- Afterbuild Labs · 10.0/10
A Base44 app stuck on Thinking is usually the editor's AI state, not your app, and the fix is Stop, Revert, and a smaller prompt. A published app that will not load is a different problem: an unpublished change, a backend function that needs redeploying, or a data permission the Security scan can flag.
What you see, and what it usually means
| What you see | What it usually means |
|---|---|
| The chat says Thinking for many minutes and nothing happens. | The AI is stuck on a large request. Stop, revert the last message, and split it. |
| Stuck on Thinking right after your very first prompt. | The app may be partially built. Clone it or start a new app with the same prompt. |
| The editor itself will not load. | Browser cache, an ad blocker or an outage. Try incognito and the status page. |
| Users see a white screen or Error 500 on the published app. | A broken change or a server-side error. Revert, then check the status page. |
| You published, but users still see the old version. | Publish did not complete, or a backend function needs Save & Redeploy. |
| Some users see data they should not, or see nothing. | Row-level permissions on an entity are wrong. Run the Security scan. |
Why it happens
Base44 is an AI app builder with its own built-in backend, owned by Wix since June 2025. Your data lives in Base44's schema-less database and your server logic runs in Base44's backend functions. There is no Supabase dashboard to open, so most problems are solved inside the Base44 editor or by its support team.
The Thinking state is the editor's AI working on your request. Base44's docs say complex first prompts can take 10 to 15 minutes, that asking the AI to undo changes does not actually revert them, and that a request stuck for more than 10 minutes should be stopped and reported. A published app that fails is usually a change that was never published, a backend function edited but not redeployed, or a permission on an entity. Base44 has a built-in diagnosis: type "Something is wrong" into the chat and it analyzes the app and suggests fixes.
Check these first
One user cannot open another user's records
Sign in as user A, copy a request from the Network tab, and change the record ID to one that belongs to user B. You should get an error or an empty result.
Access rules are on for every table
In Supabase, open Table Editor: every table should show RLS enabled, with at least one policy. In Firebase, your rules should never say allow read, write: if true.
Sign-up confirmation and password reset work end to end
Use a real inbox. Check that the link arrives, points to your live domain, and works once.
Errors reach you before users do
Add error monitoring and uptime alerts. If you learn about outages from customers, this is missing.
Database backups run automatically and a restore has been tested
Check what your database plan actually includes, then restore a backup into a test project once.
Fix it yourself
- Type Something is wrong into the AI chat. Base44 analyzes the app and lists likely causes. Check status.base44.com at the same time in case the problem is platform-wide.
- If the chat is stuck on Thinking, click Stop, then use the Revert button on the last message or open Version History (the clock icon above the chat) and restore the last working version. Do not ask the AI to undo, because that does not revert anything.
- If it stuck on your first prompt, go to Dashboard → Settings → App settings → Clone app. If the clone fails, create a new app and send the same prompt in smaller pieces.
- For a published app that will not load: confirm you clicked Publish and saw success. If you changed a backend function, use Save & Redeploy on main, then publish again.
- Switch to Discuss mode, click the broken element in the preview, and describe what it does and what it should do. Discuss mode costs about 0.3 credits per request and makes no changes.
- Open Security and run the scan. Apply its recommended fixes for any entity where users can read or edit records that are not theirs, then test with two accounts.
When to get a human engineer
Get an engineer when users can see each other's data, when the published app has been down for a day and Customer Care has not resolved it, or when you need something Base44's integrations do not do. Because the backend is Base44's, a developer works through the editor and its SDK rather than a database of their own. A one-off check costs $49 to $800 over a day to a week. A single fix is €99 to $990 and about two days. If you have outgrown the builder, moving off it runs $300 to $25,000 depending on how much has to move.
Top-rated companies for Base44 apps
Ranked by our score: published prices, scope of work, AI tools named, timing and a low-risk first step. How we score.
- 1Afterbuild Labs10.0/10Best for: A check before launchFree first step · from $49
- 2Redlab10.0/10Best for: A full rescue by one team that keeps buildingFree first step · from $490
- 3Vibe Code Rescue (Lev Arakelyan)9.0/10Best for: A one-off check and a cleanupFrom $299
Questions
Why is my Base44 app stuck on Thinking?
The editor's AI is working on a request that is too large or has stalled. Stop it, revert the last message, and resend the request in smaller steps. Over 10 minutes with no update means contact Customer Care with the prompt and the time.
Does Base44 use Supabase?
No. Base44 has its own built-in backend with a schema-less database, authentication and Deno-based backend functions, with row-level and field-level security. Wix bought the company in June 2025.
Is my Base44 app safe to launch?
Run the Security scan under Security and fix what it flags, then sign in with two accounts and confirm one cannot open the other's records. That test matters more than any scan result.
Sources: Base44 docs: Troubleshooting; Base44 docs: Backend features; Globes, 18 Jun 2025: Wix acquires Base44.
