# The BI system could not be reached

> Canonical HTML: https://screenrig.ai/problems/bi-upstream-unavailable

HTTP 500 · `bi_upstream_unavailable`

## What it means

The API answers with HTTP 500 Internal Server Error and an `application/problem+json` document when the condition is The BI system could not be reached. The document's `type` member is `https://screenrig.ai/problems/bi-upstream-unavailable`, the address of this page, and its `code` member is `bi_upstream_unavailable`.

## What to do

Check that the BI system is reachable from the public Internet and that the detail names nothing else wrong, then run screenrig bi connection test ID.

## Player action

This problem defines no Player action class. It belongs to a project, pairing or account flow that an agent or the dashboard drives.

## Reference

| Field | Value |
| --- | --- |
| Code | `bi_upstream_unavailable` |
| HTTP status | `500 Internal Server Error` |
| Type | `https://screenrig.ai/problems/bi-upstream-unavailable` |
| Player action | `none` |
| Retryable | `yes` |

- [All problem types](https://screenrig.ai/problems)
- [API reference](https://screenrig.ai/docs/api#problems)
- [Problem registry YAML](https://screenrig.ai/docs/api/problems.yaml)