ENVIRONMENT_REFUSED
Environment refused the link: what the ENVIRONMENT_REFUSED error means and how to fix it.
HTTP 409. Problem type: https://docs.ovok.com/errors/environment-refused.
What this means
The hub asked the customer environment to adopt the project you linked, and the environment refused. detail names the environment and gives its reason. The hub stores no link. The status is the environment's own, so it is 409 or 422 depending on the reason.
Troubleshooting
- Keep the project the environment already holds, or link that one instead, when the reason says the customer already has a project there.
- Check that you used the right customer and project ID when the reason says the project belongs to another customer. One project cannot serve two customers.
- Check the ID on that environment, not on the hub, when the reason says the project does not exist or is not a parent project. Link a top-level parent project, not a sub-tenant or the Super Admin project.
Retry safely
Nothing was written on the hub. Correct the project ID or the choice of project, then repeat the link. An unchanged repeat is refused again.
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 explains the response fields, and the machine-code registry lists every endpoint-specific type.
Last updated on