> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/basic-concepts/alerts-and-warnings.md).

# Alerts and Warnings

**Alerts** have been added to help you find, diagnose, and resolve common issues with your Items and Assets.

**Settings**

Alerts are on by default but can be turned off by going to the Settings > Features page:

![](/files/qTovueNpNf8Jb3o9CjnN)

**Catalog**

For example, if a rule in an Asset is malformed, you will see an Alert in the Catalog listing for any Item(s) that refer to it. You can sort Items using this column to easily find any with issues:

![](/files/ZTLxkIqav87kYZwtFwPU)

On an individual Item pages, you will see an indication by the title with a tooltip:

![](/files/fxe3QZs16QbyiRI9a16v)

In the Assigned Assets panel, you will also see an indication next to the Asset with a tooltip:

![](/files/7hPOZbDY6yboEhpVzAcE)

**Assets**

On individual Asset pages, you will see verbose alerts above the player. You can click the ⚠️ icon to expand to see multiple warnings, if applicable. From here, you can see the details of the warning and click them to go directly to what is generating them:

![](/files/yLpbzwbd70Mu6TLKoYO2)

The Editor will highlight broken or invalid references in Rule conditions and actions.

**Editor**

When working in the Editor, if the current Asset has issues in the Logic section, there will be a warning icon in the Logic tab.

The Editor's bottom Asset panel now has a tab to view Warnings for the current asset:

![](/files/Uy3VPhCOzxaHp7JkeanH)

These warnings are also linked.

*ℹ️ **Note**: for existing Organizations with existing data (e.g. Items and Assets), warning will only show once the data is viewed or updated (e.g. view and Asset or edit an Item).*


---

# 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://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/basic-concepts/alerts-and-warnings.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.