Guide

It stopped halfway

Most of the time it repairs itself. When it cannot, everything goes back the way it was.

Short answerWhen a check fails the AI rewrites and tries again — three times, then twice more on a stronger model. If that still fails it stops and rolls your project back to before the run.

What happened before it stopped

Once the code is written it is actually run. If the screen does not appear or a check fails, the AI reads why and rewrites. Three attempts, then a stronger model for two more. Stopping is the end of that ladder, not the first thing tried.

What is left behind

Nothing is left half-changed. Code and table structure go back together to where they were before this run started. An app that was working does not get broken by a request that failed.

What happens to your credits

If our side or the AI provider failed, the credits being held are released. If the AI repaired until it ran out of attempts, half comes back and you get another attempt without spending credits.

How to ask again

Narrowing the request works better than sending the same sentence a second time.

  • Ask for one thing at a time
  • Name the screen and say what is wrong with it
  • Split a big request into two or three
  • Go back to a restore point first if the app is in a strange state

What usually trips it

Being caught and repaired is far more common than stopping. The things that get caught are mostly the same few.

  • A link pointing at a screen that does not exist
  • A table left open instead of locked to its owner
  • A layout that spills sideways on a phone
  • Text too close in colour to what is behind it

If it keeps happening

A report is left where it stopped, saying what was attempted. Paste that into your message to us. The same request failing more than twice is usually something on our side to look at.

Common questions

The same sentence gave a different result. Each run is written fresh, so the words and the shape shift a little. If you want a screen to stay put, use a restore point rather than asking for it again.

It ran for ages and then stopped. It may have been waiting its turn rather than working. The screen shows where it is up to, and there is a separate guide on why builds take the time they do.

Did I do something wrong? Usually not. The one habit that does raise failures is packing several requests into one sentence. Sending them one at a time works better.

Read next

Still stuck? Check the FAQ — if it is not there either, write to us and we will answer.