# Troubleshooting

Quick fixes for the most common issues.

## The build seems stuck

* Give it a moment — first builds take up to a minute.
* If it's truly stuck, send a follow-up like "continue" or describe what you expected.
* Reload the page; your project is saved and will reopen where you left off.

## The preview is blank

* There may be a runtime error. Tell GenVibe: "the preview is blank, please fix it."
* Check that the last change finished before judging the result.

## My change didn't apply

* Be more specific about what to change and where. Use the **inspector** to select the exact element.
* If you edited code by hand, send a message so GenVibe picks up the latest files.

## I hit an error after adding a database feature

* Make sure [Supabase](/integrations/supabase.md) is connected and a project is selected.
* Describe the exact error and step that triggered it.

## A deploy failed

* Confirm the app runs cleanly in the preview first.
* Ensure required environment variables (e.g. Supabase keys) are set in your Netlify site settings.

## I ran out of credits

* **Free:** [upgrade to a paid plan](/account-and-billing/manage-subscription.md) to keep building.
* **Standard & Pro:** credits refill on your renewal date — or buy an extra credit pack to keep going now.

## The app looks wrong on mobile

* Ask: "make this fully responsive — fix the layout on small screens."

## A Pro model is locked

* Locked (🔒) models require Pro. [Upgrade](/account-and-billing/manage-subscription.md) to unlock Claude Opus.

## Something else?

If you're still stuck, restore an earlier checkpoint and try a different approach, or [contact support](/help/contact.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.genvibe.pro/help/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.