Build and customize

Fix a page that does not load

If your preview is blank or shows an error after a change, use Fix this error, Repair, Retry or Undo. Steps in the order to try them, and what each one does.

Sometimes a change leaves your page blank, or it shows an error. Your work is not lost. The agent checks every change in a live browser, tries to repair problems by itself, and gives you buttons for the rest.

Try these in order. Stop as soon as the page works.

Step Try Use it when
1 Reload preview The page looks stuck or old
2 Retry The preview did not build
3 Fix this error or Repair A card or the preview offers it
4 Tell the agent what you did The fix did not work
5 Undo this change You want the last working version back
6 Version history The problem started several changes ago

Step 1: reload the preview

  1. Click Reload preview above the preview. It is the circular arrow next to the address bar.
  2. Wait a moment. The page loads again from scratch.

This costs nothing. It does not change your files. A page can look broken only because it did not finish loading.

What the agent does by itself

After a change, the agent opens your page in a live browser and checks that it shows up. If it does not, the agent starts a repair. You may see "There were errors in the page. Trying to fix them…" in the chat.

If the repair works, you see no extra card. If the repair cannot confirm a fix, you see a card or a note, covered below.

The "Your page isn't loading" card

When the repair gives up, a red card appears above the message box:

Your page isn't loading. Something broke the page after the last change, and the automatic fix didn't confirm it.

Button What it does
Fix this error Sends the real error to the agent and asks it to fix the cause. The chat shows "Fix the page error".
Dismiss (the cross) Hides the card. Use it if the page is fine, or you will fix it your own way.

You can also type your own message: the card says "Or tell me what you were doing when it broke." Describe what you clicked, or which page you were on. That helps the agent find the cause faster.

When the preview shows the problem

If your page cannot build at all, the preview shows a panel instead of your site.

The panel says "The preview needs a fix", with one of two lines: "We detected an issue with the latest update. Click Repair to auto-fix it." or "We detected an issue with the last update." It has two buttons.

Button What it does
Repair Opens the chat and sends a fix request with the real error text. The agent works on it.
Retry Builds the preview again without changing any file. Try it first. A temporary hiccup often passes.

A different screen appears when the page loads but shows nothing. It says "App rendered nothing": "The app loaded but the screen is blank. There may be a runtime error: try refreshing or repairing." It has the same two buttons. Here Retry only reloads the page inside the preview.

When the reply says it could not fix it

A reply may end with "The app has errors I could not fix". The reply lists what is wrong. You get buttons under it:

Button What it does
Ask it to fix Asks the agent to find and fix what is still wrong
Finish the rest Asks the agent to complete anything it did not do
Keep going Asks the agent to continue from where it stopped

A reply may also say that a live check found the page was not showing correctly, and that your changes were kept. Tell the agent what looks wrong, or send your request again.

Step 4: tell the agent what you did

If the automatic fix and Fix this error both fail, use your own words. They help more than you would think. A good message names the page, what you did, and what you saw:

  • "On the Contact page, when I press Send the page goes blank."
  • "After adding the gallery, the home page shows nothing."
  • "The checkout page shows an error about a missing item."

See Write requests the agent understands.

Step 5 and 6: go back

If the page still does not work, go back to a version that did.

  • Undo this change puts the site back the way it was before the reply that broke it. It sits under that reply.
  • Version history lets you pick an earlier version. See Undo changes and restore a version.

After you go back, the page loads. Then ask for the change again, in a smaller step.

Eco and repairs

Fix this error and Repair are normal requests to the agent. Eco is used when the agent changes files to fix the page. A repair that changes nothing uses none. Reload preview, Retry and Undo this change do not use eco. See Eco: what it is and how it is used.

Other messages about the preview

Message What it means What to do
"Preview update failed. Your code changes are still saved and were not reverted." The files are saved. Only the preview did not update. Click Reload preview.
"Preview unavailable" followed by a reason, and "Your code remains unchanged." The preview could not start. Wait a moment, then Reload preview.
"Preview has newer changes from another session. Reload the project to sync this tab." You or a teammate changed the project in another tab. Reload the page.
"The preview could not set up something your app needs." A needed tool did not install. Click Retry. If it keeps happening, ask the agent to check it.
"Changes generated but not saved -- your edits may be lost on reload. Check your connection and try again." Your connection dropped before saving. Check your internet, then send the request again.
A blank page right after you typed an address that does not exist That page does not exist. It is not an error in your code. Use Back, or pick a page from the address list.

Keep errors rare

  • Make one change at a time.
  • Use Plan mode for big features. See Plan mode and Build mode.
  • Check the preview after each change before you ask for the next one.
  • Note the version number in Version history before a risky change.

If none of this works, see Troubleshooting.