What to do when the AI stops in the middle, the preview shows an error, a daily or monthly limit is reached, or a change made things worse: try again, let the AI fix it, or go back to an earlier state.
Builds sometimes stop or end with an error. Almost always nothing is lost: a build that fails before it finishes leaves your app as it was, and a change that went wrong can be undone. Find the message you see in the table, then read the details under it. How the chat works is in Build, Action and Talk.
You see | What it means | What to do
"The build stopped before it finished. Your app did not change. You can try the same request again." | The AI hit a problem mid-way. Nothing was saved. | Click 🔄 Try again under the message. It sends the same request again.
"Generation stopped" | The build was stopped. If it adds "files rolled back to previous state", the app is as it was before. | Send the request again, maybe in smaller steps.
"Error in page: …" with "AI can fix this automatically" | A page in the preview has a code error. | Click 🔧 Fix. The AI reads the error and repairs the page. 🔄 Reload loads it again.
"Something went wrong on this screen" | The screen itself crashed in your browser. | Click Try again, or reload the page.
"This page didn't load" | The connection dropped while the screen was loading. | Check your connection and try again.
"⚡ Provider unavailable - retrying with …" | One AI provider did not answer, so the Studio moved to another model on its own. | Nothing. The build continues. If it then stops, click Try again.
"Your app is still being built. Reconnecting to its progress. This new request has not run; it remains in the message box." | A build is already running for this app, for example from another tab. | Wait for it to finish, then send the text that is still in the message box.
"Build status is temporarily unavailable. Reopen the app to reconnect." | The Studio lost the live progress. The build may still be running on the server. | Close the app and open it again from My apps.
"💳 Credits exhausted" and "💳 Your credits are over. Upgrade your plan to continue." | Your build credits ran out, so the build did not start. | Upgrade, buy credits or wait for the renewal. See Credit usage.
"You've used this month's credits" with "Your request is saved and will be waiting for you after you upgrade." | The monthly credits are used. The request you typed is kept. | Pick the plan the window offers, or choose Wait until … to wait for the renewal date. See Problems with payments and credits.
"📅 You've reached today's free limit of … messages. Your daily quota resets tomorrow - or upgrade your plan to keep building right now without a daily limit." | The free plan has a daily number of builder messages. | Continue tomorrow, or upgrade on the pricing page.
"📅 You've reached this month's free limit of … messages. Your quota resets at the start of next month - or upgrade your plan to keep building right now." | The free plan's messages for this month are used. | Continue next month, or upgrade. See Plans and billing.
"Too many files for the chat" | One message can carry up to 10 files. | Click Open media library, upload the batch there, and insert the files you need into the chat.
"File "…" is too large (max 2MB). Size: …MB" | A file uploaded in the Code tab is over 2MB. | Make the file smaller (for a photo, a compressed copy), then upload it again.
1. Give it a little time: A first build of a full system can take several minutes. While it runs, the chat shows what it is doing.
2. Stop it if needed: Click Stop. If the build had already changed files, the message says whether they were rolled back to the previous state. Credits used so far are still charged.
3. Ask again in smaller steps: Instead of "build the whole clinic system", ask for one screen at a time: first the patient list, then the appointment calendar.
Describe a problem so the AI can fix it: "On the Appointments page, clicking Save does nothing and the new appointment does not appear in the list. Please find the cause and fix it, without changing the design."
Every request you sent has a revert button next to it ("Revert to state before this request"). Click it and confirm Revert: the files, data and chat from that build are removed and the app goes back to how it was before that request. Right after a revert you can undo the revert itself. Restoring needs the Atom plan or higher; on a lower plan you see "Restoring a saved version is part of the Atom plan and above. Your versions keep being saved meanwhile."
To go further back, open Versions and restore a saved version. If the app was already published, publish again after restoring so the live site matches.
The live site is safe while you fix: A broken draft does not affect the published app. Visitors keep seeing the last version you published until you publish again.
When to open a ticket: The same message comes back after two tries, the preview stays blank after a reload, or credits were charged for a build that changed nothing. Open a ticket with the app name, the time and the exact message.
Q: Did a failed build cost credits?
A: Check Credit usage; each charge is listed by app and time. A build you stopped still charges the credits it used until the stop.
Q: Try again does nothing.
A: If the request was a hidden repair (like an automatic fix), there is nothing to resend after a reload. Type your request again in the chat.
Q: The preview is blank.
A: Reload the preview. If it stays blank, tell the AI "the page is blank" and it will check the errors.
Q: Where is the daily limit shown?
A: Only on the free plan, in the message itself. Paid plans have no daily message limit.
Q: Nothing helps.
A: Open a ticket with the app name and the exact message.
Related: Saved versions and restore, Preview, device sizes and visual editing, The chat: Build, Action and Talk, Problems with payments and credits, Editing, importing and browser problems