Skip to main content
Most app problems show a message in the editor. Find the message below for what it means and what to do. For many of them, the quickest fix is to let the AI investigate:
The orders page shows a blank table. Check the logs and fix it.

​
Preview problems

The first time you open the editor after a while, the sandbox may need to install packages and start the server, which takes a moment.If it doesn’t load:
  1. Click Reload preview in the bar above the preview.
  2. Open the … menu and choose Restart server.
  3. If that doesn’t help, choose Restart sandbox. This recreates the development environment from your saved code. Your code is safe.
  4. Refresh your browser tab.
The preview server didn’t start after a restart. Refresh your browser tab. If you see the message again, try Restart sandbox from the … menu. If it persists, contact support.A similar message, “Preview server did not become ready. Try again.”, can appear after updating packages. Try the package update again from the … menu.
Vybe couldn’t recreate the sandbox. Wait a moment, then choose Restart sandbox again. If it keeps failing, contact support.
The app’s server hit an error. Click Fix with AI to send the error to the chat. The AI reads it, finds the cause and fixes it.To look at the error yourself, expand Error Details. Copy to clipboard copies the log, and Retry reloads the preview.
The app crashed in the browser. After you send a message in the chat, Vybe sends crashes like this to the AI on its own, with the error details and the page you were on, and the AI fixes the app. You don’t need to do anything. Errors the app catches and handles itself only show up in the Logs tab.
  • Vybe waits until the AI has finished responding and any build has finished, and until you’ve answered any question the AI asked.
  • It sends each error only once, and makes at most three automatic fix requests until you send your next message.
  • Clicking Stop turns automatic fixes off until you send your next message.
The same happens in an AI coworker’s chat when it shows an app preview while changing that app. The notice reads “The preview crashed. Asking the agent to repair the app…”, and the coworker fixes the app, then carries on with your request.
Open the … menu and choose the option to update packages. It reinstalls the app’s packages and reloads the preview (“Updating packages…”). If the error stays, send it to the AI.
The app’s sandbox was removed, so Vybe is recreating it from your saved code. Wait for the preview to come back. You don’t need to do anything.
Pages that need a value in the URL, like /orders/[id], can’t be opened from the page selector. Open them by clicking through the app, for example from a row in the orders list.
Nobody is signed in inside the preview, so features that depend on the current user show placeholder data there. Check them in the published app.
Large, unfiltered queries are the most common cause. Ask the AI to limit what each page loads:
Add pagination to the customers table, 25 rows per page.
The dashboard is slow. Find what’s slowing it down and fix it.

​
Chat problems

Your organization has used its credits, so the AI can’t respond. The banner offers what you can do:
  • On the Free plan: “You’ve used this month’s free credits. Upgrade to keep building, or wait for your free credits to refill on date.” Click Upgrade.
  • On a paid plan: “You’ve used all your credits. Upgrade your plan or buy more credits to keep building.” Click Buy credits or Upgrade plan.
You also can’t create new apps while you’re out of credits. See Plans and credits.
The conversation has outgrown what the model can read at once. Click + in the editor header (tooltip “Create a new conversation”) and continue in the new conversation. The AI still sees all your code and the README it keeps about the app, so you don’t lose your work.If the message mentions a shorter prompt, your last message may simply be too long. Split it up.
The model’s provider is busy. Try again in a minute, or pick a different model in the model selector.
Start a new conversation and send your request again.
“Your message was not sent. Wait for the current response to finish, then try again.” Wait for the AI to finish, or click Stop, then send your message again.
“This message is too large to send. Send it again with fewer or smaller attachments.” Remove some images, or use smaller ones. Each image can be up to 5 MB, with up to 10 per message.
Your organization pays for AI through its own gateway, and the gateway returned an error. Ask an Owner or Admin to check it. See Models and gateway.
You may be in Ask mode, which can’t change the app. Switch the mode selector to Agent, or click Switch to Agent mode if the AI shows it.
  1. Be more specific. Describe the exact behavior, data or layout you expect, and what’s wrong now.
  2. Name the page or file.
    On the customers page (src/app/customers/page.tsx), add a delete button to the last column.
  3. Break it down. Ask for one change, check it, then ask for the next.
  4. Switch models. A more capable model can help with hard bugs. See AI models.
  5. Start a new conversation if the current one is long and has gone in circles.
  6. Restore a checkpoint from before things went wrong, and try a different prompt. See Version history.

​
Build and publish problems

The app didn’t compile or a test failed. The errors go to the AI automatically, and it starts fixing them. If it keeps failing, ask it directly:
Run a type check and the tests, and fix every error.
A notice reads “App name publish failed” and “Please check the errors in the logs.” In the editor, the build logs go to the AI automatically so it can fix the problem. To read them yourself, open the Publish menu and click See errors. When the AI is done, publish again.See Publishing.
Changes in the editor don’t go live until you publish. An amber dot on the Publish button means you have unpublished changes. Open the menu and click Publish latest changes. If you still see the old version afterwards, hard-refresh the page (Cmd+Shift+R on macOS, Ctrl+Shift+R on Windows).

​
Data problems

The preview and the published app use the same database, so anything you create while testing is real data. Delete test records when you’re done, or ask the AI to help. See App data.
Restoring brings back old code but leaves the database as it is. If the AI changed tables after that checkpoint, the code and the database may no longer match. Ask the AI:
Check the database schema against the code and fix any mismatches.

​
Access problems

Only Owners, Admins and Editors can create apps. If you have one of those roles and see “Failed to create app. Please try again.”, check that your organization has credits left.
The editor shows why:
  • Access Denied: your role can’t edit apps.
  • App Not Found: the app doesn’t exist, or you don’t have access to it.
  • App Archived: restore it from the Archived filter on the Apps page.
  • Wrong Organization: click Switch Organization.
See The app editor.
Files with a gear icon are locked and read-only. Ask the AI for the change you need instead. See Locked files.

​
Use the Logs tab

The Logs tab streams the preview’s logs: server output, package installs and the browser console. It isn’t open by default. Add it from the + menu in the workspace. Look for lines that mention an error near the time the problem happened, and paste them into the chat. The AI can also read the logs itself, so asking it to “check the logs” often works just as well. The Logs tab only covers the preview. For a failed publish, use See errors in the Publish menu.

​
Contact support

If you’re stuck, email support@vybe.build or click Contact support in the user menu at the bottom of the sidebar. Include the app’s name, what you were doing, and the exact error message.