# Fixing errors

Apps break sometimes — that's normal. GenVibe is built to recover, and here's how to help it.

## GenVibe fixes many errors automatically

When your app throws a runtime error, GenVibe can detect it and attempt a fix on its own. Often you'll just see it make a correction without you doing anything.

## How to report a problem

If something's wrong and it isn't auto-fixed, describe **what you did** and **what happened**:

{% hint style="success" %}
**Good:** "When I click Save on the new-task form, the screen goes blank and nothing is added."
{% endhint %}

{% hint style="warning" %}
**Less helpful:** "It's broken."
{% endhint %}

The clearer the symptom, the faster and more accurate the fix.

## Useful details to include

* What you clicked or typed.
* What you expected vs what actually happened.
* Any error message you saw.
* Whether it happens every time or just sometimes.

## Pinpoint a specific element

If the problem is with one element on screen, use the **inspector** to select it, then describe the issue. GenVibe will focus on exactly that element.

## If a change made things worse

Restore an earlier **checkpoint** from the workbench and continue from a known-good state.

## Still stuck?

* Try rephrasing the request more specifically.
* Break a big change into smaller steps.
* Reach out via [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/guides/fixing-errors.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.
