# Device identifier is attached to more than one screen

> Canonical HTML: https://screenrig.ai/problems/recovery-ambiguous/

HTTP 409 · `recovery_ambiguous`

## What it means

The API answers with HTTP 409 Conflict and an `application/problem+json` document when the condition is Device identifier is attached to more than one screen. The document's `type` member is `https://screenrig.ai/problems/recovery-ambiguous`, the address of this page, and its `code` member is `recovery_ambiguous`.

## What to do

The device is attached to more than one screen, so recovery cannot pick one. List the screens (screenrig screen list), report the conflict, and do not retry.

## 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 | `recovery_ambiguous` |
| HTTP status | `409 Conflict` |
| Type | `https://screenrig.ai/problems/recovery-ambiguous` |
| 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)