EXPORTS_OVER_CAPACITY

Exports over capacity: what the EXPORTS_OVER_CAPACITY error means and how to fix it.

HTTP 503. Problem type: https://docs.ovok.com/errors/exports-over-capacity.

What this means

This Ovok process is already building as many night report PDFs as it allows, or its report renderer ran out of memory or queue room, so it refused this export to protect the rest. The report was not built and nothing was stored.

Troubleshooting

  1. Wait for retryAfterSec, which the Retry-After header repeats. It is at least 15 seconds.
  2. Add a random pause to each retry. Clients that retry at the same moment cause another burst.
  3. Export fewer nights per report, and start one export at a time.

Retry safely

Retry after the delay. The refused export stored nothing, so repeating it creates no duplicate report. Back off further if the error keeps coming, and never retry in a tight loop.

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