PROVISION_SECRET_UNSET

Provisioning secret not set: what the PROVISION_SECRET_UNSET error means and how to fix it.

HTTP 503. Problem type: https://docs.ovok.com/errors/provision-secret-unset.

What this means

This environment has no usable provisioning secret, so it accepts no calls from the billing hub. A secret shorter than 32 characters counts as unset. Nothing was created or changed.

Troubleshooting

  1. Ask the deployment administrator to set the shared provisioning secret on this environment and redeploy it. Use the same value as the hub.
  2. Check its length. The secret must be at least 32 characters.
  3. Check the hub too. Without a usable secret there, it pushes nothing to any environment.

Retry safely

Wait for retryAfterSec, which the Retry-After header repeats, and retry only after the environment is redeployed with the secret. Until then every call returns the same error. The hub pushes again on the next change to the customer's account and when it next starts.

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