# ENVIRONMENT_IGNORED_LINK

Canonical page: https://docs.ovok.com/errors/environment-ignored-link

**HTTP 502.** Problem type: [`https://docs.ovok.com/errors/environment-ignored-link`](https://docs.ovok.com/errors/environment-ignored-link).

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

A customer environment took the hub's push but answered with a different project than the one you linked, so it did not apply the link. This usually means the environment runs a version from before links existed. The hub keeps no link.

## Troubleshooting [#troubleshooting]

1. Deploy the environment at the same version as the hub, so it understands links. Then repeat the link.
2. Check what the environment holds for the customer. An environment that ignored the link may have created a project of its own, or answered one it already had.
3. Link that project instead if you want to keep it. After the update, the environment accepts a link to the project it already holds.

## Retry safely [#retry-safely]

Retry only after the environment is updated. Before that it gives the same answer. The hub stored nothing on this failure, so a repeat is safe.

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