Fix problems

Most problems in Buildliy have a quick fix you can do yourself. This page is organised by what you see. Find your symptom, read what it means, then follow the steps.

Before anything else, remember two safety nets:

• Every build saves a version. You can always go back to one that worked, and restoring is free (your live preview uses a small amount of credit while it's running). See Version history.
• Buildliy checks your builds and repairs many problems automatically before you see them. See How builds are checked.

The build failed

What it means: the build stopped before it could finish. The chat shows a short message in plain English that says what went wrong and what to try.

What to do: match the message to the table below. To try again, send your message again. There's no separate retry button.

If a build stopped partway (for example, because it ran too long), work the AI finished before it stopped is kept. Check the preview, then send a focused follow-up to carry on.

A request that's too big is the most common cause. Instead of asking for everything at once, go step by step:

Let's do this in steps. First, add just the homepage with a hero section and a contact button. Don't add the booking system yet.

Your app shows an error

What it means: the code was written, but a page crashes when it loads.

What to do:

1. If the preview says This preview hit an error, click Fix it. The AI gets the error and makes the smallest change that gets the page loading again. It's a normal build, so it uses credits.
2. If the AI's reply says one page hit an error after it checked your app, reply "fix it", or describe what you want changed.
3. If Fix it doesn't solve it, describe what you were doing when it broke. That gives the AI more to go on:

The /checkout page shows an error since I asked for a discount code box. Please find what's causing it and fix it with the smallest change. Keep everything else exactly as it is.

If it still won't load, restore the last version that worked and ask for the change again in smaller steps.

The preview is blank or "waking up"

What it means: your preview runs on its own little server, which goes to sleep when you haven't used it for a while. Waking it up takes a moment.

The home page shows a blank white screen in the preview. Please find out why nothing is showing and fix it.

A page is missing

What it means: you've gone to an address that isn't a page in your app. The preview says This page doesn't exist yet.

What to do:

1. Click the page path above the preview (such as /) to see the Discovered pages in your app, and pick one. You can also type an address under Go to path and press Enter.
2. To see every page and how they link together, open Workspace → App map.
3. If the page should exist, ask for it. If a button or link goes to the wrong place, say which one:

Add an About page at /about with our story and team photos, and add an "About" link to the menu on every page.

The "Book now" button on the home page goes to a page that doesn't exist. Make it open the booking page instead.

The AI changed something you didn't want

What it means: the AI sometimes changes more than you asked, or interprets a request differently from what you meant.

What to do: go back, then protect what you want to keep.

1. 1

   Restore the version you liked

   Hover over an AI reply that changed your app and click the circular arrow (Restore this version), or open Build history (the clock icon at the top of the chat) and click Restore on any version. Restoring is free (apart from the preview's running time), and both versions stay in your chat history so you can move forward again. To undo only the most recent build, click your project's name and choose Undo last build.

2. 2

   Ask again, more precisely

   Say exactly what should change and what must stay the same.

3. 3

   Protect the parts you want to keep

   Choose any of these:

   • Lock a file. In the Code tab, hover over a file and click the lock icon. The AI's changes to locked files are blocked, and if a request needs one, it's told to ask you to unlock it.
   • Keep an element as is. Click the arrow icon above the preview to pick an element, then click Keep as is on the chip that appears above the chat box. The AI is told to leave it alone in later builds. To undo it, delete its line in Workspace → Knowledge.
   • Write a standing rule in Workspace → Knowledge, such as "Never change the logo or the footer." See Project knowledge.

Only change the colour of the "Sign up" button to green. Don't change anything else on the page.

The AI is stuck or going in circles

What it means: big changes can take several minutes, so a long build isn't always stuck. But sometimes the AI gets stuck trying the same fix over and over.

What to do:

1. Give it a moment. The status under the build says what the AI is doing, and bigger changes can take a few minutes. On a first build, if the AI has been quiet for several minutes, the preview area says so.
2. Steer it. While a build is running, type a note in the chat box and keep Add to this build selected. Your note joins the build at its next step, without starting over.
3. Stop it. Click the stop button in the chat box (Stop current build). Work already written is kept, and you're charged for the work already done (every build uses at least 1 credit). The project owner and Admins on the team can stop any build; Members can stop builds they started. Stopping also pauses Up next until you click Resume all.
4. Change your approach. Restore the last good version, then ask again in smaller steps, or switch to Discuss to talk the problem through before building.

Builds also have a maximum running time. If a build reaches it, it's wrapped up automatically, the changes the AI had finished are saved, and the chat says "This build ran out of time before I could finish." Send a focused follow-up to continue.

When you ask again, give the AI the facts it was missing:

The contact form still doesn't send. When I click Submit, nothing happens and the form stays filled in. I expected a "Thanks!" message and the message saved in the database. Please find the cause before changing anything, then fix only that.

You ran out of credits during a build

What it means: builds use credits as they go. A build that's already running still finishes if your credits run out partway. Anything past zero shows as owed on the Credits card, and the next credits you add pay that first. New builds need at least 1 credit.

Publishing failed

What it means: your app couldn't be put live, or a new update didn't go out. If your app was already live, the previous version stays up ("Your live site is still up — the latest update didn't publish.").

What to do:

Publishing failed with "The published build didn't compile." Please find and fix the error so the app builds cleanly, without changing how it looks.

Your custom domain isn't working

What it means: your domain's DNS records don't point at your app yet, or they've changed. Custom domains are part of Pro.

Each domain shows a status:

What to do:

1. Open Publish → Connect (or Workspace → Launch) and find your domain. Its setup panel lists the records to add. Compare each record with what's at your domain provider. The type, host and value must match exactly.
2. Delete any old records Buildliy lists under "Then delete these old records".
3. If your DNS provider can route traffic through its own proxy (some show this as an orange cloud icon), turn the proxy off for these records so they're "DNS only". Otherwise the security certificate can't be issued.
4. Click Check now. Buildliy also checks automatically while the page is open. Most providers go live in 5–30 minutes, but a few take up to 48 hours.

See Custom domains for step-by-step setup.

Sign-in emails aren't arriving

Emails from Buildliy to you

For your own Buildliy account (confirming your email or resetting your password):

1. Check your spam or junk folder.
2. On the Check your email screen, click Resend email.
3. For a password reset, use Forgot password? on the sign-in page and open the link in the same browser.
4. If a link says it has expired or was already used, request a new one.

Emails from your app to your users

The built-in sign-in on Buildliy hosting lets people sign up with an email and password and sign in straight away. It doesn't send any emails (no confirmation email and no "Forgot password?" email), so there's nothing to wait for. If someone can't get in:

• Open Manage → Users to check they've signed up.
• For password-reset emails, turn on Social login & password reset (Beta) in Manage → Users. See User sign-in.
• If your app uses your own Supabase project, its sign-in emails are sent by Supabase. Check its email settings, and whether the person has confirmed their email, in your Supabase dashboard.

To have your app send its own emails, connect an email service and ask for it in chat. See Send email and User sign-in.

Payments aren't working

What it means: most often, your app is still in test mode, or your Stripe account isn't fully set up.

What to do: open Payments in the left sidebar of your dashboard and read the status at the top.

If payments are set up but a button still doesn't work, tell the AI exactly what happens:

On the pricing page, clicking "Buy" on the Pro plan does nothing. It should open checkout for $29. Please find the cause and fix it.

See Take payments.

Ask for fixes that work

The AI fixes problems best when it knows exactly what's wrong. A good fix request says:

• Where: the page or part of the page. Use the arrow icon above the preview to point at the exact element.
• What you did: the button you clicked or the text you typed.
• What you expected, and what happened instead.
• The exact error text, if there is one.
• What must not change, so the fix stays small.

If the AI has tried twice and the problem is still there, stop and change approach: restore a version that worked, then ask for the change in smaller steps.

Still stuck?

Search the FAQ, or contact the team with a link to your project and what you've tried.

Related

• How builds are checked
• Version history
• Credits and usage
• Get help