Skip to main content
This page covers the most common issues you may run into while building with Vybe, along with steps to resolve them.

​
Common issues

The live preview may fail to load for several reasons:
  1. The sandbox is starting up. The development sandbox takes a few seconds to initialize when you first open an app or after a period of inactivity. Wait a moment and the preview will load automatically.
  2. A server error is preventing the page from rendering. Open the Logs tab in the editor to check for server-side errors. If you see errors, describe them to the AI:
    The preview is not loading. The logs show a “Cannot find module” error. Can you fix it?
  3. A build error is blocking the preview. Ask the AI to run a type check:
    Run a type check and fix any errors.
  4. The page has a client-side error. Open your browser’s developer console (F12) to check for JavaScript errors. Send any error messages to the AI for debugging.
If none of these steps help, try refreshing the page or creating a new browser tab.
Deployment can fail if your app has unresolved code issues.
  1. Run type checks before deploying. Ask the AI to verify your code:
    Run a type check on the project and fix any issues before I deploy.
  2. Check the deployment details. When a deployment fails, the deployment status page shows the specific error message and the build step that failed. Use this information to guide the AI:
    The deployment failed with this error: [paste error]. Can you fix it?
  3. Common causes of build failures:
    • Missing imports or undefined variables
    • TypeScript type errors
    • Incorrect API route function signatures
    • References to files that have been deleted
Make it a habit to ask the AI to run type checks before every deployment. This catches most issues before they reach the build step.
If an integration is not working or data is not flowing:
  1. Verify you completed the connection flow. Go to the Integrations page and check that the integration shows as connected. For OAuth-based integrations, you may need to re-authorize if the token has expired.
  2. Check visibility settings. Integrations can be scoped to “You only” or shared with the organization. If another team member cannot use an integration, it may need its visibility updated.
  3. For database connections:
    • Verify the connection string is correct (host, port, database name, credentials)
    • Check that your database’s firewall allows connections from Vybe’s IP addresses
    • For SSH tunnels, confirm the public key is added to the server’s authorized_keys file
  4. For third-party services:
    • Confirm the API credentials are valid and have not been rotated
    • Check that the required scopes or permissions are granted
    • Review the service’s status page for outages
If the AI’s output does not match what you asked for:
  1. Be more specific. Vague prompts lead to guessed implementations. Add detail about the exact behavior, layout, or data you expect.
  2. Reference specific files. Instead of “update the customers page,” try:
    Update src/app/customers/page.tsx to add a delete button in the last column of the table.
  3. Break it down. Large, multi-step requests are more prone to errors. Split them into smaller prompts:
    First, add the delete button to each row.
    Then:
    Now add a confirmation dialog that appears when the delete button is clicked.
  4. Switch models. If the current model is struggling, try Opus 4.5 - High for more careful reasoning, or a different provider for a fresh approach.
  5. Start a new thread. If the conversation has become long and cluttered, a new thread gives the AI a cleaner context to work from.
If you are approaching your credit limit:
  1. Switch to a cheaper model. Haiku 4.5 uses the fewest credits per interaction. Use it for simple edits and quick questions.
  2. Use Ask mode for questions. Ask mode interactions typically consume fewer credits than Agent mode since the AI does not execute tools.
  3. Check your plan. Review your plan’s credit allocation and renewal schedule in your organization settings.
  4. Upgrade your plan. If you consistently hit your credit limit, a higher-tier plan provides more credits per billing cycle.
Credit usage varies by model and response length. Complex interactions with Opus 4.5 - High use significantly more credits than simple Haiku 4.5 queries.
If queries against a connected external database are not working:
  1. Verify the connection string. Go to Integrations and confirm the host, port, database name, and credentials are correct.
  2. Check read-only mode. If the connection is configured as read-only, write operations (INSERT, UPDATE, DELETE) will be blocked. This is intentional for data safety.
  3. For SSH tunnels:
    • Confirm the SSH host and port are accessible from Vybe
    • Verify the public key is in the remote server’s ~/.ssh/authorized_keys
    • Check that the SSH user has permission to forward connections
  4. For Amazon Redshift:
    • Verify IAM role permissions if using IAM-based authentication
    • Check that the Redshift cluster is publicly accessible or reachable from Vybe’s network
  5. Test with a simple query. Start with SELECT 1 to verify basic connectivity before running complex queries.
If your deployed app looks outdated:
  1. Confirm you deployed after making changes. Changes in the editor are not automatically deployed. Click Deploy to publish the latest version.
  2. Check deployment status. The deployment may still be building. Wait for it to complete before testing.
  3. Clear your browser cache. Cached assets may show an older version. Try loading the app in an incognito window or hard-refresh the page (Cmd+Shift+R on macOS, Ctrl+Shift+R on Windows).
  4. Check the deployment URL. Make sure you are visiting the correct deployment URL, not an old preview link.
If you added or modified database tables but the changes are not reflected:
  1. Ask the AI to apply the migration. Schema changes need to be applied to the database:
    Apply the pending database migration.
  2. Check for migration errors. The AI will report if a migration fails due to conflicts or invalid SQL.
  3. Verify in the Data tab. Open the Data tab in the editor to see the current database schema and confirm your changes are applied.
If the preview takes a long time to load or the app feels sluggish:
  1. Check your data queries. Large, unfiltered queries are the most common cause of slow pages. Add pagination, filters, or limits:
    Add pagination to the customers table — show 25 rows per page.
  2. Look for unnecessary re-renders. If using client components with frequent state updates, ask the AI to optimize:
    The dashboard feels slow. Can you check for performance issues and optimize the rendering?
  3. Add loading states. While data fetches, show skeleton loaders or spinners so the page feels responsive:
    Add loading skeletons while the data is being fetched.

​
Getting more help

If you cannot resolve an issue using the steps above:
  • Ask the AI. Describe the problem in detail and the AI will investigate your code, logs, and configuration to find the root cause.
  • Contact support. Reach out to the Vybe team at [email protected] with a description of the issue and any relevant error messages.

​
What’s next