When it goes wrong

The build will not finish

First, check the clock against real numbers. Seven real builds took 221 to 616 seconds. Anything under ten minutes is probably just working.

Then look at the tray. If your job says waiting, another one is running — one job runs at a time, and yours starts when that finishes.

If it stopped instead, we tried to repair it and could not. Half the cost comes back, and you get one more attempt at no charge. Before pressing it, cut the request down: ask for one page instead of six.

The preview will not open

If the build has not finished its first run, there is nothing to open yet. Wait for it to say done.

A blank page right after a change usually means the newest version is still being built. Give it a moment and reload.

If it stays blank, go back to the last restore point. That returns you to a version that was known to work, and it costs nothing.

You are out of credits

A free account gets 30 credits a month. Building from nothing takes 6 of them, so a heavy day runs the balance down.

Move the small work off your balance: change wording and colours by clicking them in the preview, which costs nothing, and keep credits for real features.

Ask for one thing at a time. One clear request at 2.75 beats three vague ones that need redoing.

Paid plans are not switched on yet, so more credits cannot be bought today. If you are stuck, tell us.

You cannot sign in

Check you are using the address you signed up with. An account made with Google is a different account from one made with the same address and a password.

If sign-up seems to do nothing, try a private window. An old session in the browser is the usual culprit.

Repeated sign-in attempts from one place get slowed down on purpose. Wait a few minutes rather than trying harder.

Still stuck

Tell us what you asked for, what came out, and roughly when. That is enough for us to find the job and look at it.

If it is blocking your business, say so. We would rather hear it early.