# ENVIRONMENT_PROJECT_EXISTS

Canonical page: https://docs.ovok.com/errors/environment-project-exists

**HTTP 409.** Problem type: [`https://docs.ovok.com/errors/environment-project-exists`](https://docs.ovok.com/errors/environment-project-exists).

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

The customer already has a project on that environment, because the environment answered with one earlier, so Ovok refused to link another. A link applies only until the environment has answered a project for the customer.

## Troubleshooting [#troubleshooting]

1. Read `detail`. It names the project the customer already has on that environment.
2. Check whether that is the project you meant to link. If it is, the request is already satisfied, and sending the same link again succeeds without changing anything.
3. Keep working with the existing project if you wanted a different one. The hub does not replace a project the environment has already answered.

## Retry safely [#retry-safely]

Do not retry the same link for a different project. It is refused again, and nothing was written.

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