When something goes wrong
What to do when the preview won't load, a change comes out wrong, a request fails or you run out of credits, and how to go back to an earlier version.
First steps
Refresh the preview
Use Refresh preview. Many loading glitches go away this way.
Read the message in the preview or the chat
It says what happened and, most of the time, comes with a button to fix it.
Go back to a version that worked
Restoring uses no credits and doesn't delete any version.
Ask again, smaller and clearer
Describe what you see, where you see it and what you expected.
The preview doesn't show or shows an error
| Message | What to do |
|---|---|
| The preview didn't load | The connection dropped while the preview engine was loading; it isn't an error in your site. Click Try again. |
| The preview couldn't be built | The site's code didn't compile. Click Ask the AI to fix it: the error goes to the chat as a normal request. |
| The site hit an error | The site broke when it opened. Use Ask the AI to fix it or restore the previous version. |
| 1 image didn't load | The image's address doesn't exist or blocks access. Use Ask the AI to replace them to swap it. |
Note.Forms don't send messages from the preview. To test a form, publish the site, fill it in at the published address and check the entry under Leads.
A change came out wrong
- Right after the change, use Undo this change in the chat.
- In the Code tab, under See changes, Undo in this file reverts a single file, when that doesn't break the rest of the site.
- In History, pick an earlier version and click Restore. This creates a new version identical to the one you picked, and nothing is lost.
- In a code project you can also type “go back to version 3” in the chat; it offers the restore button, at no cost.
Important.Restoring brings back that version's code. The site's data, such as sign-ups, tasks and orders, doesn't come back with it and stays as it is.
A request failed
| Message | What it means |
|---|---|
| Something went wrong while preparing your changes | The request failed, the site wasn't modified and the credits were refunded. Try again, ideally with a smaller request. |
| This request was cut off before it finished | The server restarted during the work. Nothing changed in the code and the credits came back; send it again. |
| You're sending requests quickly | Wait a moment and send it again. |
| The AI builder is temporarily unavailable | The AI service didn't respond. The site wasn't changed; try again later. |
You ran out of credits
With the Not enough credits for this request notice, the chat shows what the request needs and what you have, and suggests smaller parts with Use this request. When the balance reaches zero, your sites stay online and you can still edit by hand, publish and restore versions. To get more credits, see AI credits.
The published site doesn't show the change
Changes show in the preview first. To put them online, click Publish (in the visual editor, Publish changes). If a new publish brought a problem, publish an earlier version again from History. For address problems, see Domain troubleshooting.
The AI keeps trying to fix it and the error stays. What do I do?
Stop repeating the same fix. Restore the last version that worked and ask for the change another way, in smaller parts. To understand the cause before touching the code, describe the problem in Plan mode.
Did I lose credits on a request that failed?
No. Requests that fail, don't pass the checks or are cut off give their credits back. Check it on AI usage.
Does restoring delete the newer versions?
No. Restoring creates a new version identical to the one you picked; every other version stays in the history.
When should I contact support?
When the problem persists after restoring a version that worked, when a payment doesn't show up or when the published site goes offline for no clear reason. See Getting help.
Related articles
Still need help?
Our team answers within one business day.