Logs and errors

Things sometimes go wrong: a page stops loading, a key stops working, or something changes in your data that you didn't expect. This page covers where to look, and how to get problems fixed without needing to read code.

Manage → Logs

Open the Manage tab and choose Logs. If your app reports its own errors, you see two tabs: Your app, which opens first (see Errors from your live app), and Activity.

Activity is a running record of what happens in your app's backend, newest first. For example, you'll see entries when:

• the AI creates a table for your app
• a query runs in the SQL editor
• a secret is added, changed or deleted
• a folder is created, or files and folders are deleted, in Storage
• your data is rewound or put back from a backup
• your app's database or published pages are paused because your account ran out of credits, and when they start again

Each entry shows when it happened (the time, plus the date for anything before today), a level (info, warn, error or debug), where it came from, and a short message. Click an entry to see more detail, when it has any.

Filter and follow logs

• Search messages… finds entries containing the words you type.
• Last hour, Last 24h and Last 7d set the time range.
• All, Info, Warn, Error and Debug filter by level. Pick Error to see only problems.
• Live adds new entries as they happen. Click it to switch to Paused when you want the list to stay still, and click again to resume. The refresh button reloads the list.

If nothing happened in the range you picked, you'll see No logs in this range.

Logs record backend activity, not every visit to your app. To see who visits your live app, use Analytics.

Errors while you build

Most problems show up in the preview while you're building.

• This preview hit an error. The page didn't load correctly. Click Fix it and the AI runs a repair build, which uses credits like any other build. Or describe what's wrong in the chat instead.
• Something works, but not the way you want. Describe what you see and what you expected. The more specific, the better.

When I click "Book now" on the class page nothing happens. It should save the booking and show a confirmation.

If you see an error message in your app, copy it into the chat. The AI can use the exact wording to find the cause.

Buildliy also checks your app after each build and tries to repair pages that don't load before handing it back to you. See How builds are checked.

Errors from your live app

New apps report their own errors to Manage → Logs: problems on your app's server, and errors in visitors' browsers. Only your published app reports, not the preview, so errors start to appear after you publish. If you published before reporting was added, publish again.

Open Manage → Logs and choose Your app. Each error gets one card:

• Error or Warning, and the error's message.
• How often it happened in the time range you picked (for example "Happened 12 times"), when it last happened, the page it happened on, and whether it happened on the server or in visitors' browsers.
• Show details for the technical details, when there are any.

Pick Last 24 hours, Last 7 days or Last 14 days at the top. When the same error happens again, it's counted on its card instead of added as a new one. The list refreshes by itself while it's open.

Click Fix it to put a request to fix that error in the chat box, with the error's details. Nothing is sent until you review it and press send. Sending it runs a normal build, which uses credits, and the fix reaches your live site when you publish again.

Error reports don't use credits. As the tab says: "Visitors' emails, passwords, keys and tokens are hidden before anything is saved. Errors are kept for 14 days. You and your teammates can see them." Reports never include the form data or cookies sent with a visitor's request, and the page is saved without the part of its address after a "?".

For an app made earlier, ask the AI to add error reporting, then publish again.

Set up error reporting so errors from my live app show up in Manage → Logs.

Live-site health checks

Once your app is published, Buildliy checks your live site every hour. Each check loads your home page and up to two other pages from your app (it skips pages like sign-in, account and admin pages).

If two checks in a row fail, Buildliy alerts you once for that problem:

• In the chat, with a card titled Your live site has a problem. It says what went wrong, when it was first noticed, and "I check every hour."
• By email, with the subject "Your live site has a problem".

On the card you can:

• Click See details to see the site's address, the page that failed, the pages that were checked and when the last check ran.
• Click Fix it to ask the AI to find and fix the cause. This runs a normal build, so it uses credits. The fix reaches your live site when you publish again.
• Click Hide to dismiss the card.

When your site works again, the chat shows a short "Your live site is back up." line. If you were emailed about the problem, you also get an email titled "Your live site is back up". The Launch tab (Workspace menu → Launch) also shows the latest result, such as "Live site: working · checked 20 minutes ago".

You get at most one problem email and one "back up" email for each problem. To avoid a flood of emails from a site that keeps dropping out, Buildliy also doesn't send a new problem email within a day of the last live-site email for that app; if the problem is still there after that, the email goes out then. The chat card shows every problem.

When to ask for help

If the AI can't fix a problem after a couple of tries, see Fix problems for common causes and next steps, or Get help to contact the team.

Related

• How builds are checked
• Fix problems
• Publish your app
• The Manage tab