> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/good-to-know/troubleshoot/errors-after-importing.md).

# Errors after importing

You can still preview your app if you see these warnings. They are here to inform you of the various reasons that may cause differences between your design file and the app preview in Bravo Vision.

## **Container missing: a container has been auto added**

This warning occurs when Bravo has added a missing container, which specifies the main structural blocks of an app page.

{% hint style="success" %}
**How to solve:** This warning doesn't require any action unless your app preview in Bravo Vision looks different from your design. Bravo functions on a "container" method, check out this [documentation](broken://pages/-MfgiCryp4HdueTetP8C) on how to set up your design file with containers.
{% endhint %}

## **Out of the container: \[Element] is out of the parent bounding box and can be incorrectly visualized.**

This occurs when a visual element is outside of a [container](broken://pages/-MfgiCryp4HdueTetP8C). Preview your app in Bravo Vision first to see if it looks different from your design. If it doesn't, you can skip this warning.

{% hint style="success" %}
**How to solve:** Click `Fix` to locate the element in your design file. Place the element within its parent container.
{% endhint %}

## **Unexpected element: \[Element] cannot be a \[Bravo Tag]**

This occurs when a Bravo Tag is placed on an element that is not compatible with the specific tag, so the Bravo Tag will not work.

{% hint style="success" %}
**How to solve:** In this [Bravo Tag table](https://www.notion.so/523e067121054c84a6d5b8bb87dd00b0), under the column **Layer Type**, you can see which type of element works with each Bravo Tags.
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.bravostudio.app/good-to-know/troubleshoot/errors-after-importing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.