# custom_indicator_unavailable

A custom indicator the run uses could not be installed on the machine.

## What happened

A run that uses your own indicators installs them on the machine first. When that fails, the run ends with this code and the machine's reason in `detail.reason`. A different code, `custom_indicator_not_available`, is the refusal when an indicator is not yours or is not runnable.

## What to do

Check the indicator, save a version that passes its checks, and start the run again.

## Example

```json
{
  "status": "failed",
  "error": {
    "code": "custom_indicator_unavailable",
    "message": "A custom indicator this run uses is no longer available.",
    "detail": {}
  }
}
```