# DOCUMENT_CONTENT_MISSING

Canonical page: https://docs.ovok.com/errors/document-content-missing

**HTTP 422.** Problem type: [`https://docs.ovok.com/errors/document-content-missing`](https://docs.ovok.com/errors/document-content-missing).

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

A DocumentReference POSTed to `/fhir/R4/DocumentReference` has an attachment that holds no document: neither `data`
nor `url`, or no `content` at all. Nothing was stored.

## Troubleshooting [#troubleshooting]

1. Put the document in each `content.attachment`, base64-encoded in `data` with its `contentType`; Ovok stores it as a
   Binary and sets `url` to it.
2. Or point `url` at a document already stored, such as `Binary/<id>`.

## Retry safely [#retry-safely]

Safe to send again once every attachment holds its document.

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