> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getinteract.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Systems

> View the health of your connected data sources and browse system event logs.

The Systems page shows the current status of all connectors in your organization alongside a log of technical events from the past 90 days. Use it to spot problems early and investigate what happened.

## Connector status cards

At the top of the page, each of your connected data systems appears as a card. The card shows:

* **Connector name and type** (for example, BigQuery)
* **Status indicator** — whether the connector is healthy or has experienced recent errors
* A quick link to the relevant log entries

If a connector has no recent events, it shows as healthy. If it has logged errors or anomalies recently, the card highlights that.

## Event log

Below the connector cards, a filterable table lists all system events. Each row shows:

| Column        | Description                           |
| ------------- | ------------------------------------- |
| **Date**      | When the event occurred               |
| **Connector** | Which data source triggered the event |
| **Topic**     | The type of event (see below)         |
| **Level**     | Severity — `error` or `warning`       |
| **Message**   | A description of what happened        |

### Event types

| Topic         | What it means                                                   |
| ------------- | --------------------------------------------------------------- |
| `failed_run`  | A scheduled job or data query could not complete successfully   |
| `anomaly`     | An unexpected pattern or value was detected in the data         |
| `failed_send` | A notification could not be delivered to the configured channel |

### Filtering events

Use the filter controls above the table to narrow down results:

* **By connector** — show events from a specific data source only
* **By date range** — the log goes back 90 days
* **By level** — filter for errors only, or include warnings too

## What to do when you see an error

1. Click the row to expand the full message — it often contains the specific error detail from the data source
2. If the error is a **failed run**, check whether the underlying data source is available and the connector credentials are still valid (see [Connectors](/org-settings/connectors/overview))
3. If it is an **anomaly**, review the flagged data in your agent or report to assess whether action is needed
4. If it is a **failed send**, verify that the notification channel is still configured correctly (see [Notification channels](/org-settings/notifications/setting-up-channels))