# LOCATION_HAS_RESIDENT

Canonical page: https://docs.ovok.com/errors/location-has-resident

**HTTP 409.** Problem type: [`https://docs.ovok.com/errors/location-has-resident`](https://docs.ovok.com/errors/location-has-resident).

## What this means [#what-this-means]

A location (a room or bed) holds one resident. The save would have put a second resident in a location that already has one, so Ovok refused it and wrote nothing. `params.locationId` names the location.

A device, resident or location save can put a resident in a location: assigning a resident to a device in it, or moving a device that has a resident into it.

## Troubleshooting [#troubleshooting]

1. Find who is in the location: `GET /v1/slim/location/{locationId}` answers its resident as `patientId`.
2. Unassign that resident first, or move them to another location, then save again.
3. To give the same resident a second device in the location, assign that resident. One resident on several devices of a location is allowed.

## Retry safely [#retry-safely]

Retrying the same save gets the same answer until the location is free. Nothing was written, so a retry after unassigning the resident cannot duplicate anything.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
