# PUSH_PROVIDER_UNAVAILABLE

Canonical page: https://docs.ovok.com/errors/push-provider-unavailable

**HTTP 502.** Problem type: [`https://docs.ovok.com/errors/push-provider-unavailable`](https://docs.ovok.com/errors/push-provider-unavailable).

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

Ovok could not check the push provider's credentials: the provider could not be reached in time, or it answered with an error of its own. Nothing was stored.

## Troubleshooting [#troubleshooting]

1. Wait a short while and send the request again. Provider outages are usually brief.
2. Check the provider's status page if it lasts. For FCM this is Google's token service.
3. Check that the server can reach the provider over the network, if this happens on a self-hosted deployment.

## Retry safely [#retry-safely]

Retry after a short wait. Nothing was stored, so the retry starts from the same state.

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