# Screen cannot set its volume

> Canonical HTML: https://screenrig.ai/problems/volume-unsupported

HTTP 409 · `volume_unsupported`

## What it means

The API answers with HTTP 409 Conflict and an `application/problem+json` document when the condition is Screen cannot set its volume. The document's `type` member is `https://screenrig.ai/problems/volume-unsupported`, the address of this page, and its `code` member is `volume_unsupported`.

## What to do

This screen's Player cannot set its volume remotely. Update the Player to its current version, or set the volume in the Player's settings menu.

## Should you retry?

The `retryable` member appears only on HTTP 5xx problems, so this one has none. Follow the steps under What to do before sending the request again.

## Example response

Most routes answer with the error in the first entry of `errors`, and the document members `instance` and `request_id` beside it. The `type`, `code`, `title` and `status` of this problem type are fixed; `detail` varies per request, and `hint` is the registry default unless the handler sets a more specific one.

~~~http
HTTP/1.1 409 Conflict
Content-Type: application/problem+json

{
  "errors": [
    {
      "status": 409,
      "code": "volume_unsupported",
      "type": "https://screenrig.ai/problems/volume-unsupported",
      "title": "Screen cannot set its volume",
      "detail": "What went wrong in this request.",
      "hint": "This screen's Player cannot set its volume remotely. Update the Player to its current version, or set the volume in the Player's settings menu."
    }
  ],
  "instance": "INSTANCE",
  "request_id": "REQUEST_ID",
  "server_time": "2026-01-01T00:00:00Z"
}
~~~

## In the API contract

The OpenAPI contract describes this problem in these words:

> What the Player reached is reported back in its health volume (Screen.volume.reported). The screen must be active (an archived screen answers screen_archived, a pairing_pending one resource_conflict) and its host hint must declare the volume capability, else 409 volume_unsupported and nothing is recorded.

## Operations that name this problem

These operations name this problem in the API reference:

- [Set Screen Volume](https://screenrig.ai/docs/api/screens#op-setScreenVolume) — `POST /api/screens/{id}/volume`

## Related problems

The contract mentions these problems alongside this one:

- [Resource state conflicts with the request](https://screenrig.ai/problems/resource-conflict) — `resource_conflict`
- [Screen is archived](https://screenrig.ai/problems/screen-archived) — `screen_archived`

## 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 | `volume_unsupported` |
| HTTP status | `409 Conflict` |
| Type | `https://screenrig.ai/problems/volume-unsupported` |
| Player action | `none` |

- [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)
