ENVIRONMENT_NOT_PUSHED

Environment is not pushed to: what the ENVIRONMENT_NOT_PUSHED error means and how to fix it.

HTTP 422. Problem type: https://docs.ovok.com/errors/environment-not-pushed.

What this means

Ovok refused to link a customer's project on an environment because this deployment does not push customers to that environment. Nothing was sent to the environment.

Troubleshooting

  1. Check that you run the link on the billing hub. Only the hub, the deployment that takes payments, pushes customers.
  2. Check that the environment in the path is staging or production, and that the hub's list of customer environments names it with its API base URL.
  3. Check that the hub has a usable provisioning secret of at least 32 characters. Without one, the hub treats its list of customer environments as empty.

Retry safely

Nothing was written. Retry after the deployment administrator has fixed the hub's configuration. 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