# Alerts

See the errors and warnings Risotto raised for your organization in the last 14 days, and dismiss the ones you have dealt with

The **Alerts** page lists the errors and warnings that Risotto raised for your organization in the last 14 days, such as a connected system that rejected Risotto's credentials or a request that Risotto could not process. Only Org Admins and Managers can open it.

## Open the Alerts page

Click the organization menu at the top of the sidebar, then click **Alerts**. The menu item shows the number of open alerts.

*Product example: The organization menu in the Risotto dashboard's sidebar, open, with Alerts and its count of 3 open alerts.*

While at least one alert is open, an **Alerts** button also shows next to the organization name. Its dot is red when an open alert is an error, and the warning color otherwise. Hover over the button to see the count, for example "Alerts · 3 open". When the sidebar is collapsed, the button is in the rail, under **Search**.

## The alerts list

The page lists the open alerts from the last 14 days, under an **Errors** heading and a **Warnings** heading. Alerts with the same title are grouped in one row. Each row shows:

- The title, a one-line summary, such as **Okta Connection Error**.
- A preview of the message.
- How many times the alert was raised, for example `3×`, when it was raised more than once.
- When the most recent one was raised.

*Product example: The Alerts page in the Risotto dashboard: 3 open alerts under Errors and Warnings, with the Okta Connection Error open to its full message.*

Click a row to open its full message in place. The message links to the dashboard page where you can fix the problem. When Risotto could not process a request, the message names the ticket or the Slack thread and the person who asked, an **Additional details** block, and an **Error code** that you can quote to Risotto support. It also notes that the Risotto team has been notified and will follow up if it is a system issue. Under the message, Risotto shows the severity and when the alert was first and last raised. Click the row again to close it.

The bar above the list shows how many alerts are open. The page loads the 200 most recent alerts. When there are more, the bar also shows how many older alerts are not shown. When there are none, the page reads **No open alerts**.

## Dismiss alerts

Dismiss an alert once you have dealt with it, so the list and the count show only what still needs you.

- To dismiss one alert, click **Dismiss** (the check mark) at the end of its row.
- To dismiss every alert under a heading, click **Dismiss all errors** or **Dismiss all warnings**. The button shows when the heading has more than one alert.
- To dismiss several alerts, check the box at the start of each row, or check the box in the bar to select every row. Then click **Dismiss** in the bar. The button shows the number of rows you selected.

*Product example: The Alerts page in the Risotto dashboard with the Okta Connection Error checked and Dismiss 1 in the list bar.*

Dismissing a row dismisses every alert in its group, for everyone in your organization. If the problem happens again, Risotto raises a new alert.

## Connection alerts

When a connected system rejects Risotto's credentials, Risotto adds an alert here. If your organization has a [notifications channel](https://www.tryrisotto.com/docs/dashboard/settings/notifications), Risotto also posts the alert there. This covers Okta, Google Workspace, Jamf Pro, Iru, Microsoft Intune, Confluence, and the credentials of a tool.

Risotto raises the alert when a call fails. It does not test your connections on a schedule, so an expired key can stay quiet until the next request needs it.

When a knowledge index fails, Risotto adds an **Indexing Job Error** error with the failure message and a link to **Knowledge > Indexes**.

The notifications channel also gets informational messages that are not errors or warnings. The Alerts page does not list those.

## Credential alerts

When Risotto refuses to send a [Credential Vault](https://www.tryrisotto.com/docs/dashboard/settings/credential-vault) credential to a host outside its allowed hosts, it adds the error alert **Vault Credential Blocked by Allowed Hosts**. A refusal in an Assistant script adds no alert. The alert links to the credential. Add the host to the credential's allowed hosts, or correct the destination where the credential is used.

## Ask the Assistant about alerts

Org Admins and Managers can ask the [Assistant](https://www.tryrisotto.com/docs/dashboard/assistant) why something they set up is not working. The Assistant reads the same alerts that this page lists: errors and warnings from the last 14 days that nobody dismissed. It cannot dismiss alerts.

## Permissions

Only **Org Admins** and **Managers** can open the Alerts page and see the **Alerts** item and button in the sidebar.

Source: https://www.tryrisotto.com/docs/dashboard/alerts
