When something goes wrong
What each BurrowHub message or stuck screen means and what to do: opening apps, signing in, builds, previews, data, domains, and asking for help.
On this page
First checks
Most problems clear up with one of these. Try them in order before anything else.
- Reload the page. An app that was resting wakes up in a few seconds, and a reload often shows it.
- Check you're in the right business. Look at the business name in the switcher. A consultant working for several clients sees each one as "Client: …"; switch to the one that has the app.
- Check whether you're looking at the preview or the live app. A change waits as a preview that only the people who build the app can see. Everyone else keeps seeing the live version until it's published.
- Wait a minute and try again. Many messages below say "Try again in a moment" because the problem passes by itself.
Opening an app
- "Opening …" with "It was resting to save energy. This takes a few seconds." — Nothing is wrong. Apps nobody is using rest, and this page wakes them. Wait; the app opens by itself.
- "Waking up…" — "This app is starting. This page will refresh by itself." BurrowHub is restarting for a moment. Leave the page open.
- "… could not start" — "It did not come back from resting." Press Try again; that often works. If it keeps happening, the app needs a look: ask whoever builds it to try a rebuild, or ask BurrowHub.
- "This app didn't answer" — The app was woken several times in a few minutes and still didn't respond. Wait a few minutes, then open it again. If the same app does this every time, its last version is likely broken: put an earlier version back (see versions).
- "That link has expired" — The sign-in link into the app is used up or too old. Open the app again from BurrowHub.
- "No app here" — "This app doesn't exist or isn't ready yet." Check the address. A new app has no address until its first version is built; wait for the build to finish.
- "This app isn't in your hub" — You're signed in, but in a business that doesn't have this app, or the app isn't shared with you. Switch to the business that has it, or ask its owner or an admin to share it with you.
- "Something went wrong" — "Try again in a moment." Do that. If it stays, note the time and ask BurrowHub.
Inside an app, a screen may show one of these instead (in English): This app is starting. Try again in a moment. and This app couldn't start. Try again in a moment. mean the same as the pages above. This app has too many live connections right now. Try again in a moment. means too many screens are watching the app live at once; close tabs you don't need and try again. Sign in to BurrowHub to use this app. means you were signed out: sign in and open the app again.
Signing in and access
- "Email or password is incorrect." — Check the address is the one you were invited with, and the password. Typing it wrong several times shows "Too many attempts. Please try again in 15 minutes." Wait 15 minutes; trying sooner doesn't help.
- "Your account isn't in a business yet" — Your account isn't part of a business right now. See what to do.
- "Partners can build and change this business's apps, and nothing else here." — You're working as a partner (consultant). Members, billing, settings, uploading data and connecting Google Drive stay with the business. Ask its owner or an admin to do that part.
- A client disappeared from your switcher, or you see "That partner access no longer exists." — The business removed your access. That takes effect at once, and the apps you made stay theirs. Ask the business to give access again with your partner code.
- "No business has that partner code. Check it with them." or "That doesn't look like a partner code." — The code is 12 letters and numbers, like
ABCD-EFGH-JKLM. If the partner made a new code, the old one stopped working.
When a build doesn't work
A failed build shows "… hasn't been built yet" for a new app, or "That change didn't go through" for a change. A failed change never touches the app people use: "Your app is exactly as it was — nothing was lost, and you can keep using it." Under the title, one line says what kind of problem it was:
- "Something went wrong on our side, not with what you asked for." — Press Try again. Don't reword your request; it was fine.
- "The AI couldn't make this one work." — Press Describe it differently. Ask for less at once, name the screen and the fields, or split it into two changes. See change in small steps.
- "It ran out of time rather than going wrong." — Try again, or ask for something a little smaller.
- "This was stopped before it finished." — Someone pressed stop. Nothing changed; send it again when you're ready.
- "We're not sure what went wrong this time." — Try again once. If it fails the same way, describe it differently.
"Waiting for a turn to start…" means the build is in line behind another build of the same app, or others. It starts by itself. "The AI is still working on your last message." means one change is still building: write the next one now and send it when that's done.
Builds left, estimates and Auto mode
- "No builds left for today" — Your business has used all of today's builds. Everyone who builds in the business shares them, and a new app, a change or a retry each use one. They come back one at a time, 24 hours after each was started — the screen says when the next one is available. Everything already built keeps working.
- "Building is paused" — BurrowHub has paused building new apps for your business. Your apps keep working.
- "We couldn't work out an estimate. Nothing was built." — Press Try again. Nothing was charged.
- "Worked out without AI, so it cost nothing." — The estimate was made from the words in your request, not by the AI, so it can miss parts of a bigger app. If the features listed look too few, press Try again — a retry gets another chance at the AI — or describe the app in more detail.
- "Auto mode paused: this change could cost more than your … limit." or "… more than your business has left this month." — Auto mode only builds on its own within your limit. Check the estimate and approve it yourself, or raise the limit.
- "Building with AI isn't switched on here, so new messages can't be sent." — You can still try, publish and restore versions.
Preview, publishing and going back
- "I changed it but my team still sees the old app." — The change is waiting as a preview. Open the app's Live and preview, try it, then press Publish. Everyone gets it at once.
- Data I entered in the preview is gone. — The preview uses a copy of your data, so nothing you do in it changes the live app. Enter real data in the live app.
- "The preview can't be shown inside this page" — Your browser didn't let the app sign you in inside the page. Press Open in a new tab; it works the same there.
- "A newer preview arrived a moment ago. Have a look at it before you publish." — Someone else (or the AI) built a newer change. Try it, then publish.
- "That preview isn't waiting any more." — Someone may have just published or discarded it. Reload to see what is live now.
- "This version needs more than your business's plan allows, so it can't go live." — Ask for a smaller change, or ask BurrowHub about your plan.
- A change broke the app. — Put the earlier version back under History → Restore. Choose Code only to keep today's data. See versions and restore.
- "Putting the data back with version … didn't work. The app kept the data it had." — Nothing was lost. Try again later, or ask BurrowHub.
- "Changes go live as soon as they're built, so there's nothing to preview." — Publish changes automatically is on for this app. An owner or admin can turn it off so changes wait as a preview again.
Data that doesn't update
- An app shows old numbers from a connected file. — Connected files are read again on a schedule, not instantly. Open Your data, choose the file and press Refresh now.
- "Google stopped letting BurrowHub read your Drive." — Google access was taken away (for example the password changed or access was removed). Apps keep reading the last good version. An owner or admin presses Connect again.
- "The last refresh didn't work" — Check the file still exists and the connected account can open it, then press Refresh now.
- "Google Drive wasn't connected: the permission was declined." — Connect again and allow BurrowHub to read your files when asked.
- "Your data changed shape" — A column or sheet was added or removed since the app was built. New rows need nothing, but new columns do: press Rebuild with the new columns. It uses one of today's builds.
- "That file couldn't be read." — Open it in Excel or Google Sheets and save it again as .xlsx or .csv, then upload it again.
- A partner can't add or connect data. — That stays with the business. A partner can see which data the client has and build on it; an owner or admin adds and refreshes it. See getting your data in.
A device or game can't connect
Some apps also take direct connections from a game, a device or another program. They are listed on the app's page under Connections from devices and games, and nothing can connect until an owner or admin allows it.
- "Waiting for you to allow it" — Nobody has allowed this connection yet. Read why the app needs it, then press Allow (or Allow without a key, when the app checks devices itself). It opens within a minute. A new version that changes how the connection works asks again.
- "Only the business's owners and admins can allow or stop a connection." — Members and partners (consultants) can see the connection but not allow it. Ask an owner or admin.
- "Stopped" — An owner or admin stopped it, and nothing can connect. Press Allow to open it again.
- "… connections without a valid key were refused" — A device sent no key or the wrong one. It must send the line BH-TOKEN followed by the Connection key first. After New key, devices using the old key are disconnected and need the new one.
- "The app no longer asks for this connection." — You tried to allow or stop a connection that the live version doesn't use any more. Reload the page. To bring it back, ask the AI for it in a new change.
- "We couldn't load this app's connections." — Press Try again. "That didn't work. Please try again." — Nothing was changed; press the same button again.
Your own domain isn't working
- "Waiting for your records" — BurrowHub hasn't found the two records yet. Add both where you bought the domain, exactly as shown. New records can take a few minutes, sometimes up to a day. Then press Check now.
- "Not found yet" — The line under it says why. "We looked for the first record (TXT) and didn't find it": check its name — many providers add your domain to the name for you, so type only the short form the page shows. "We found a TXT record there, but it holds a different value": copy the value again exactly. "We couldn't reach the internet's address book (DNS) just now": nothing changed; try again in a minute.
- It says "Working" but visitors don't arrive. — The check looks at the first record (TXT). Check the second record, the one that sends visitors to the app, is there and exactly as shown.
- A domain that worked stopped working. — BurrowHub checks the records every hour; if they are removed, the address stops working. Put the records back and press Check now.
- "This BurrowHub can only open addresses with a prefix." — Use the
www.address instead, and ask the place you bought the domain to forward the bare domain to it. - "Only owners and admins can change this app's domain." — Ask an owner or admin of the business. Partners can't set domains.
Building with your own Claude
If Claude can't reach BurrowHub, a connection wasn't allowed, a check is out of date, or a preview link shows the live app, see troubleshooting your own Claude. Each preview from your own Claude also uses one of the business's builds for the day, so "No builds left for today" above applies there too.
Consultants: for how to work on a client's apps from start to finish, see Building apps for clients.
Asking BurrowHub for help
If you work for a client, ask the client's owner or admin first: many fixes (access, data, domains, sharing) are theirs to make. To reach BurrowHub, use Talk to us at the bottom of BurrowHub's front page, or Contact us on the "Your account isn't in a business yet" screen. Both open an email to hello@burrowhub.com.
- The app's name and its address
- The business it belongs to, and whether you're a member or a partner
- When it happened: the date, the time and your time zone
- The exact message, copied word for word (and, for a failed build, what "For developers: what the builder reported" says)
- What you clicked or asked for just before
- Whether it was the preview or the live app, and the version number
- A screenshot of the whole screen
- Whether it happens every time, and on which device and browser