# CLIENT_NOT_FOUND

Canonical page: https://docs.ovok.com/errors/client-not-found

**HTTP 404.** Problem type: [`https://docs.ovok.com/errors/client-not-found`](https://docs.ovok.com/errors/client-not-found).

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

Signals found no client with that ID in the tenant that fits the request, so it changed nothing. When attaching a client to a patient, the client must exist in the same tenant, be named by its client ID, and have a role that fits: a submitter or admin for the submitters, a subscriber for the subscribers. System clients cannot be attached.

## Troubleshooting [#troubleshooting]

1. Name the client by its `clientId`, not by its Signals `id`.
2. Check the client's role against the list you attach it to.
3. List the tenant's clients to confirm the client exists in this tenant.

## Retry safely [#retry-safely]

An unchanged request returns the same error. Nothing changed, so a corrected request is safe to send.

## 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.
