A build stopped or failed

Most builds end with a short summary. When a build ends early, the last message in the chat says why, in a red box or in Crisp's own words. Find your case below.

Stopped after reaching the step limit#

A single build can only take a certain number of steps. Large requests sometimes need more. The work done so far stays in place.

1. 1 Look at the preview to see how far Crisp got.
2. 2 Send: "Continue where you stopped." Crisp remembers the conversation and picks up the rest.
3. 3 Next time, split a large request into smaller ones. See Write good prompts.

Paused at your limit#

The request reached your limit per request. Its work so far stays in your app, and nothing past the limit is charged. Press Continue to let Crisp pick up where it stopped, or Change the limit first. See How AI usage is charged.

Out of usage#

Your balance is used up, so new requests cannot start. Your message goes back into the box, and the chat says when your usage renews. Top up or upgrade on the Billing page, or wait for the renewal. Everything else, including your published apps, keeps working.

The AI service is busy#

A note such as The AI service is busy. Trying again (2 of 5). means the AI service did not answer the first time. Crisp tries again by itself, and the build goes on. If the note says Crisp has reached its AI limit for now, the build continues at the time it shows. You do not need to do anything.

An error while working#

Something went wrong during the build. A build that ends with an error is not charged, and the line under the reply says so. Send your request again. If the same error comes back, the second attempt is not charged either, and the chat offers Try a different approach: use it rather than asking for the same fix a third time.

Crisp could not fix a problem#

When the same error comes back three times, Crisp stops instead of trying forever. It explains the error in plain words, says what it tried, and gives you two or three options. Reply with the option you prefer, or with more detail about what you want.

Something waits on you#

If a feature needs a key from another service, Crisp builds everything else and names the missing key in its summary. See Give your app a key.

The app broke after a change#

1. 1 Say what is wrong, on which page, and what you did: "Since the last change, the bookings page shows an error when I open it."
2. 2 If you see an error message, copy it into your message.
3. 3 Crisp can read your app's error log, so it often finds the cause even when the page only says that something went wrong.

A build is already running#

Only one build runs at a time in each project. Wait for it to finish, or press Stop, then send your message.

Still stuck#

Write to us through the contact form with the name of your project and what you tried. A person reads every message.