Account and reference · Chapter 28

Chirai error guide

Ten short videos, one for each kind of problem people run into most while building, changing and publishing. Each shows what you see, why it happens, how to fix it yourself, and what to say to IILA. The steps are written out under each video.

Chirai finds and repairs most problems before you see them, and repairs are never charged. When one still gets through, find it here.

If you see…Go to
The progress hasn’t moved for many minutesThe build stopped, or says “Build failed”
“Something went wrong” where the page should beA page says “Something went wrong”, or is blank
“Publishing failed” after pressing ↑ PublishPublishing failed
A list with nothing in itA list is empty, or a form won’t save
“Wrong email or password”Can’t sign in, or sent back to the sign-in page
Checkout fails at the last stepPayments don’t go through
“Pending” on the Domains pageMy domain stays “pending”
The wrong colourIt doesn’t look the way I asked
“Your request, line by line: 78% built”Something I asked for isn’t there
“Couldn’t load the latest”My phone app shows nothing, or its test build fails
TipThe fastest fix is almost always the same: tell IILA what is wrong and on which page, one thing at a time.

The build stopped, or says “Build failed”

You see one of these:

  • The progress hasn’t moved for many minutes
  • “Build failed” in the Studio
  • “Request timed out”

Why it happens: A build is about 40 minutes of writing and checking. It stops when the model Chirai is writing with goes quiet, when a page it wrote doesn’t compile, or when the preview doesn’t start in time.

What to do:

  1. Read the reason. A failed build shows its real reason in the Studio, in one line. (Build failed · Request timed out · The preview couldn’t start)
  2. Press Fix with IILA. IILA reads the error and repairs the file it points to. Repairs are never charged. Where — In the Studio: The error panel → Fix with IILA.
  3. Still failing? Press Try again. Try again picks the build up again. Your description and answers are kept. Where — In the Studio: The error panel → Try again.
  4. Failed twice? Send us the reason. Email the error line and your app’s name. Every one is read. Where — Write to: support-note@chirai.dev · The error line, copied · Your app’s name.

When it's sorted: The preview opens. From there you change anything by asking IILA or clicking on it.

A page says “Something went wrong”, or is blank

You see one of these:

  • “Something went wrong” where the page should be
  • The menu shows, the page under it is empty
  • It worked a moment, then broke

Why it happens: The page opened, then failed while loading its data: a part it relies on is missing, or the data came in a shape the page didn’t expect.

What to do:

  1. What you see. The rest of the site works. One page, or a few, shows an error screen. (Something went wrong · Sorry about that — please try again.)
  2. Chirai checks this for you. After every build each page is opened in a real browser. A page that crashes is repaired and opened again before you see it. Where — In your build story: Repaired 2 pages that crashed · or: 1 page still breaks: /portfolio.
  3. Ask IILA to fix it. Name the page. IILA gets the exact error the browser saw. Where — In the Studio chat: Open the chat → Name the page → Send. Say to IILA: Fix the crash on the Portfolio page
  4. Run the Test Agent. It opens every page on desktop and phone, presses the buttons, and lists what is broken with a Fix button. Where — In the Studio: Studio → Test Agent.

When it's sorted: Every page opens. If the story still names a page, press Try again on the build. Repairs are never charged.

Publishing failed

You see one of these:

  • “Publishing failed” after pressing ↑ Publish
  • An error naming a page, like /menu
  • It worked in the preview

Why it happens: Publishing makes a stricter, production build on the host (Vercel). A page that worked in the preview can fail there, and a busy host can ask Chirai to slow down.

What to do:

  1. Read the two lines. The first line names the page. The second is the real reason — that is the one that matters. (Error occurred prerendering page "/menu" · ReferenceError: Suspense is not defined)
  2. Press Fix with IILA. It repairs from the host’s full build log, not just the headline, then publishes again by itself. Where — In the Studio: The publish error → Fix with IILA.
  3. If it says the host is busy, wait. Chirai waits 30 seconds, then 60, then 120, and tries again by itself. Pressing Publish many times makes it worse. Where — What to do: Leave the tab open · Don’t press Publish again · It carries on by itself.
  4. Check your plan. Putting a site live needs Starter ($10 a month) or above. A free build stays in the preview. Where — On chirai.dev: Pricing → Starter — $10 a month → ↑ Publish.

When it's sorted: Your site is live. Chirai opens the live site and checks it. Later changes go live by themselves.

A list is empty, or a form won’t save

You see one of these:

  • A list with nothing in it
  • “Please sign in first”
  • A message naming a field

Why it happens: Your site shows what is in its database. A new site has only a few sample records, some things can only be saved by a signed-in person, and each field has rules that came from your description.

What to do:

  1. Read the message. It names the field and says what it needs, and the field is highlighted. (Please sign in first · Phone needs 10 digits · Description must be at least 20 characters)
  2. Empty list? Add your records. Products, projects, classes, prices: everything the site lists is added here. No code. Where — In Chirai: ⚙ Manage site → Records → Add.
  3. “Please sign in first”. The page saves something that belongs to a person, like an order or a booking. Sign in on your site, then try again. Where — On your site: Sign in → Go back to the page → Save again.
  4. A rule you don’t want? Ask IILA. Rules come from your description. IILA changes them in the page and the database together. Where — In the Studio chat: Open the chat → Name the page and the field → Send. Say to IILA: On the Contact page, make Phone optional

When it's sorted: Your lists fill, your forms save. What you add in Manage site is on the live site within a minute.

Can’t sign in, or sent back to the sign-in page

You see one of these:

  • “Wrong email or password”
  • “Please confirm your email first”
  • Signed in, but no admin pages

Why it happens: Most sign-in trouble is one of three things: the account was made with Google and has no password, the email was never confirmed, or you are signed in as a visitor and not as the admin.

What to do:

  1. Sign in the way you signed up. Signed up with Google? Use Continue with Google — that account has no password. Signed up with email? Use the password, or reset it. Where — On chirai.dev: Sign in → Continue with Google → or: Forgot password.
  2. Confirm your email. A new account gets one email with a link. Check spam. The link signs you in. Where — In your inbox: From Chirai (or your site) → Confirm your email.
  3. To run your site, use the admin account. The admin of your site is the email of your Chirai account. Your build story names it. Others who sign up are visitors until you give them a role. Where — In your build story: You’re the admin · Sign in on your site with that email.
  4. Phone apps. Apps Chirai builds sign in with email and password. Google sign-in isn’t in apps yet. Where — In the app: Create account → Email and password → Sign in.

When it's sorted: You’re in. Stuck on a site you built? Run the Test Agent: it signs in with a temporary account and tells you what fails.

Payments don’t go through

You see one of these:

  • Checkout fails at the last step
  • Orders stay “awaiting payment”
  • No way to pay shows up

Why it happens: Money goes into your own payment account, with your own keys. Payments fail when test keys meet a real card (or the reverse), when the payment account isn’t activated for live payments, or when you use your own payment link.

What to do:

  1. Check which keys are in. Start with test keys and the provider’s test card. Switch to live keys only when a test order goes through. Where — In Chirai: ⚙ Manage site → Payments → Test keys first, then live keys.
  2. Activate your payment account. A new Razorpay or Stripe account takes test payments at once, but live payments only after you finish their sign-up. Where — At your payment provider: Your dashboard → Finish activation → Live mode: on.
  3. Using your own payment link? Chirai can’t see a payment made on a link. The order waits until you mark it paid. Where — In Chirai: ⚙ Manage site → Orders → Mark as paid.

When it's sorted: A test order goes through. Then put in your live keys. Chirai never takes a cut of your sales.

My domain stays “pending”

You see one of these:

  • “Pending” on the Domains page
  • The address opens nothing, or an old site
  • “Not secure” in the browser

Why it happens: A domain points at your site through two small records at the place you bought it. It stays pending until those records match exactly and have spread across the internet.

What to do:

  1. Copy the records exactly. At your registrar, add what the Domains page shows. No extra dots. Use @ for the root. Where — The records: A @ 76.76.21.21 · CNAME www cname.vercel-dns.com.
  2. On Cloudflare: DNS only. A proxied (orange cloud) record hides the address Chirai needs to see. Set it to DNS only (grey cloud). Where — In Cloudflare: DNS → The record → Proxy status: DNS only.
  3. Press Check now. Records can take a few hours to spread. Chirai also checks every 10 minutes for two weeks and emails you when it is live. Where — In Chirai: Domains → Your site → Check now.

When it's sorted: Your domain is live, with https. Chirai makes the certificate and republishes the site on the new address.

It doesn’t look the way I asked

You see one of these:

  • The wrong colour
  • Text that is hard to read
  • It breaks on a phone
  • A photo that doesn’t fit

Why it happens: Chirai designs from your words. What you don’t say, it decides: the colour, the style, the photos.

What to do:

  1. Ask IILA, one page at a time. Name the page and say what you want to see. Changes never use up your plan. Where — In the Studio chat: Open the chat → Name the page → Send. Say to IILA: On the home page, make the buttons green and the headline smaller
  2. Or click what you want to change. Click a text or a photo in the Studio and change it right there. Where — In the Studio: Click the text or photo → Type, or choose a photo → Save.
  3. Hard to read, or broken on a phone? The Test Agent looks at every page on desktop, phone and tablet and lists these with a Fix button. Where — In the Studio: Studio → Test Agent.
  4. Next build: say the colour and the feel. A colour you name becomes the brand colour. A feeling helps too: “calm”, “bold”, “like a magazine”. Where — In your description: “White background, green accent” · “Calm and airy, big photos”.

When it's sorted: It looks like yours. Use your own photos and words: Manage site keeps them when the design changes.

Something I asked for isn’t there

You see one of these:

  • “Your request, line by line: 78% built”
  • A button that does nothing
  • A menu link to a page that isn’t there

Why it happens: A long request is built in order of importance, and Chirai then checks your request line by line. What didn’t make it is listed in your build story, in your own words.

What to do:

  1. Open your build story. It lists what was built and exactly what wasn’t. Where — In the Studio: Build story → Your request, line by line.
  2. Ask IILA for one line at a time. Use the story’s own wording. One thing per message works best. Changes never use up your plan. Where — In the Studio chat: Open the chat → One thing → Send. Say to IILA: Add the Contact page with a form that reaches my inbox
  3. Buttons and links. The Test Agent presses every button and follows every link, and lists the ones that go nowhere. Where — In the Studio: Studio → Test Agent.
  4. Next time: fewer, clearer lines. Say the pages, what each one is for, and what people can do on it. The docs have seven questions that help. Where — In the docs: Docs → How to write the best prompt.

When it's sorted: Your request, fully built. The story shows 100% when every line is there.

My phone app shows nothing, or its test build fails

You see one of these:

  • “Couldn’t load the latest”
  • Empty screens in the phone preview
  • The Android test build failed

Why it happens: The phone preview can show sample data or your app’s real data. On real data a new app has almost nothing in it yet. A test build is made by a build service that can be busy.

What to do:

  1. Look at which data the preview shows. Sample data fills every screen so you can judge the design. Real data shows what is really in your app. Where — In the Studio: Phone preview → Sample data · Real data.
  2. Add your records. What you add here shows in the app on real data. Where — In Chirai: ⚙ Manage site → Records → Add.
  3. Run the Test Agent. It opens every screen, signs in with a temporary account, tests the signed-in screens, then deletes the account. It lists what is broken. Where — In the Studio: Studio → Test Agent.
  4. Test build failed? Try again. Most failed test builds are the build service being busy. If it fails twice, the log names the reason — send it to us. Where — In the Studio: Ship → The test build → Try again.

When it's sorted: Your app runs on your phone. If a store says no, watch “If the store says no” in the publishing guide.

Still stuck

Email support-note@chirai.dev with the message you see and your app's name. For store questions, the Studio's publishing guide has its own videos, including “If the store says no”. More short answers are in Troubleshooting.