The build stopped before it finished
Why a change sometimes ends early, what state your site is left in, and how to pick it up again.
Occasionally a change ends before it is finished. Spanli is built to stop and say so rather than churn away quietly, so when this happens you get told what happened in the chat.
Your site is never left broken by it. What was already done is kept, and you can carry on.
Read what it says
The message in the chat is the useful part. It will be one of these:
"You have run out of credits." The work costs more than you have left. See I've run out of credits.
It ran for too long. Very large requests hit a time limit. Ask for the same thing in smaller pieces — one page rather than the whole site, one section rather than one page.
It finished, but with things it could not fix. Spanli does not loop forever on a problem it cannot solve. After a few attempts it stops, finishes the job, and tells you plainly what is still off. That is a deliberate choice: you would rather know than have it grind.
You pressed stop. Nothing else happened. Ask again whenever.
What to do next
- Look at your site in the preview. Most of the time you will find the work is largely there.
- Say "carry on", or ask for the remaining part specifically. The conversation has not lost anything — it remembers what you were doing.
- If it came out worse than it went in, put the site back to before you started. See Putting things back.
Making big requests smaller
This is the single best thing you can do about it. Instead of:
"Rebuild the whole site with a new look, new photos everywhere, three new pages and different wording."
ask for it in four goes. Each one is faster, cheaper, easier to judge, and if one goes wrong you only put back that one.
When it keeps happening
If the same request fails repeatedly, say so in the chat — "this is the third time this has stopped" — and describe what you were asking for. Rewording a request is often enough, and Spanli will tell you when what you are asking for is not something it can build.