> For the complete documentation index, see [llms.txt](https://docs.genvibe.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.genvibe.pro/help/troubleshooting.md).

# 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 model is locked

* Premium models show a lock (🔒) on the Free plan. [Upgrade to any paid plan](/account-and-billing/manage-subscription.md) — Standard or Pro — to unlock all frontier models.

## Something else?

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.