NO_OWNER

Project has no owner email: what the NO_OWNER error means and how to fix it.

HTTP 422. Problem type: https://docs.ovok.com/errors/no-owner.

What this means

Ovok refused to link the customer's project on an environment because the project has no owner with an email address. The environment needs an owner to become the first admin of the project it creates or adopts.

Troubleshooting

  1. Check that the customer's parent project on the hub has an owner set.
  2. Check that the owner's user has an email address. A user without one cannot be provisioned.
  3. Give the project a real owner with an email, then repeat the link.

Retry safely

Nothing was sent or written. Retry after the owner is set. An unchanged retry returns the same error.

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

On this page