Base44 Stuck on "Thinking"? Here's How to Fix It (2026)
Jump to: stuck mid-project · stuck on the first prompt · Stop button doesn't work · when it's not just a freeze
Start Here: Is It Actually Stuck?
- Check the clock, not your patience. Base44's own guidance: click Stop once the processing state has run past 10 minutes, or sooner if it stops giving any updates at all — whichever comes first. A complex first prompt on a brand-new app can normally take 10-15 minutes, so don't stop it early just because it feels slow.
- Check status.base44.com. If Base44 is reporting an incident, nothing on your end will unstick it — wait it out and retry once the status page clears.
- Note where it froze. Was the app already working before this prompt (go to stuck mid-project), or is this the very first prompt on a new app that's never finished loading (go to stuck on the first prompt)? Base44 treats these two cases differently, and so does this guide.
Your App Already Existed, and the Chat Froze Mid-Prompt
What you see: the chat has been on "Thinking", "Applying changes" or "Undoing" for several minutes with no updates, on an app that was working before this prompt.
Why it happens
Base44 doesn't publish an exact cause, but the fixes it recommends point at the same handful of triggers: a prompt that's too long or asks for too many things at once, a browser issue (cache, an extension, a flaky connection), or a temporary problem on Base44's side.
How to fix it
- If the state has lasted more than 10 minutes, or hasn't updated in a while, click Stop.
- Click the Revert icon on that chat message to undo the stuck prompt, or open Version History (the clock icon in the AI chat) and restore the last version that worked — check the timestamp first, since anything built after that version gets discarded.
- Rule out your browser: refresh and check your connection, clear your browser cache, turn off extensions, or open the app in a private/incognito window.
- Resend the request as two or three smaller prompts instead of one large one.
What you should see: the chat returns to an empty message box, and the app shows the version you reverted to, with no prompt still "running" in the background.
The Chat Is Stuck on "Thinking" After Your Very First Prompt
What you see: you typed your first prompt to create a brand-new app, and the chat has been on "Thinking" since, with nothing built yet, or only part of the app appearing.
Why it happens
Base44 documents this as a separate case from a mid-project freeze. A long, detailed first prompt asking for many features at once is the most common self-inflicted cause; normal complex first prompts can still take 10-15 minutes on their own.
How to fix it
- If it's genuinely gone past 10-15 minutes with no change, go to your app's Dashboard, open Settings → App settings, click Clone app, and open the cloned copy. Base44 documents this as the recommended recovery step: the app has often been partially created, and cloning gives you a working copy to continue from.
- If cloning doesn't help, copy your original prompt text, create a new app, and paste the same prompt in — but split it into smaller, sequential prompts this time (for example: "set up the data model first", then "add the main page", then "add the login screen") instead of one prompt asking for everything.
What you should see: the cloned or new app starts building normally instead of sitting on "Thinking".
If Stop Doesn't Work and You Can't Revert
What you see: you've clicked Stop, but the chat is still frozen, and Revert or Version History won't respond either.
How to fix it
Base44's documentation gives this specific sequence for exactly this case:
- Open Version History (the clock icon in the AI chat) and try restoring from there directly, instead of through the chat.
- Change the AI model your app is using — click the current model's name at the bottom of the AI chat (this needs the Builder plan or higher) — then switch to Discuss mode and send a short message such as "hi". That alone is often enough to break the stuck state, because Discuss mode runs on its own model and doesn't touch your app's code. Discuss mode costs about 0.3 credits per message (Base44's usage unit — check your balance under your workspace's Settings → General → Credit usage), typically cheaper than a full Build prompt, since Build cost scales with what you ask for.
- Make one small manual edit in Edit mode (manual edits don't use AI or credits) to force the app into a different state.
- If you're on a phone or tablet, try opening the app there, switching to Discuss mode, and sending a prompt — Base44 lists this as a separate fallback.
What you should see: the chat accepts a new message again. Once it does, go back to reverting the prompt that got stuck in the first place.
When "Stuck Thinking" Points to a Bigger Problem
A one-off freeze is normal. Treat it as a pattern worth fixing, not just clicking through, if:
- It happens on almost every prompt, not just occasionally — that usually means your prompts are consistently too long or too vague, not that Base44 is malfunctioning.
- It gets worse the longer a single chat session runs. This isn't something Base44's documentation states directly, but it's worth testing yourself: if freezes get more frequent late in a long project chat, try continuing the same work in a fresh chat session before assuming something is broken.
- It happens on a brand-new, near-empty app with a trivial prompt. That points at a Base44-side issue rather than your project — check status.base44.com and, if it's clear, contact support with the details below.
If none of the fixes above resolve it and the freeze keeps recurring, contact Base44 support directly (see what to include) rather than repeating the same steps.
One Thing to Get Right: Where Large Files Belong
If you're trying to work around a freeze by moving large assets out of your prompts or code, put them in Base44's own file storage (the built-in upload integration), not in an external service. Base44 ships with its own database, authentication and file storage — it doesn't run on Supabase, so there's no Supabase Storage bucket to move anything into.
When It Isn't a Bug
- Very long or very detailed prompts are naturally slower, first prompt or not. Splitting a request into smaller, sequential prompts isn't a workaround for a bug, it's how Base44 expects complex builds to be made.
- A live Base44 incident. If status.base44.com shows one, waiting is the fix, not retrying the same prompt repeatedly.
What to Include When You Ask for Help
If you contact Base44 support (requires login) about a freeze, include:
- where in the app the AI got stuck (which page, feature or function);
- the exact prompt or action you were running;
- how long the processing state lasted;
- whether it was your first prompt on a new app or a change to an existing one.
Frequently Asked Questions
Why does Base44 keep "Thinking" and never respond?
Usually a prompt that's too long or asks for too much at once, a browser issue, or a temporary problem on Base44's side. Check status.base44.com first, then click Stop if the state has run past 10 minutes or stopped giving updates, and revert the stuck prompt.
How long should I wait before assuming Base44 is stuck?
Base44's own guidance is to stop a normal prompt after 10 minutes, or sooner if it stops giving updates. The exception is your very first prompt on a brand-new app: a complex one can take 10-15 minutes to complete normally, so give it longer before you stop it.
Will clicking Stop or refreshing lose my work?
No. Stop only cancels the prompt that's currently running; it doesn't erase anything already built. After stopping, use the Revert icon on that chat message or Version History to get back to the last version that worked, rather than leaving the app in a half-applied state.
My app is stuck on "Thinking" right after my very first prompt — is that different?
Yes. Base44 handles this as a separate case: go to Dashboard, then Settings, then App settings, and click Clone app to open a working copy. If that doesn't help, copy your original prompt, start a new app, and send it again split into smaller, sequential steps.
Neither Stop nor Revert is working. What now?
Try Version History directly, then switch your app's AI model and send a short message like "hi" in Discuss mode — that alone often breaks the stuck state, since Discuss mode runs separately from Build. If that doesn't help, make a small manual edit in Edit mode to force a state change. If you have a phone or tablet handy, you can also try the same Discuss-mode message from there.
My Base44 app isn't loading at all — is that the same as being stuck on "Thinking"?
No, they're different problems. "Stuck on Thinking" is the AI chat frozen while it builds or changes something. An app or preview that won't load, shows a blank screen, or fails only for other people (not you) is usually a publishing, visibility or browser issue instead — see the full Base44 not working guide for those.
Related
If the chat isn't just slow but genuinely broken alongside other errors — the editor won't load, the app shows a blank screen, or you're seeing 429s and credit errors too — see the full Base44 not working guide.
Still broken after this guide?
If your Base44 app keeps failing in ways this guide doesn't cover, the AppStuck Master Prompt gets your AI builder to write up the problems in your app, so you can see what's wrong before you change anything else. It's free. Get the Master Prompt.
Sources
Checked on September 22, 2026:
