Error reference / not-ready
Sealed document is not ready yet
The sealed PDF is still being produced.
| Problem type | /problems/not-ready |
|---|---|
| HTTP status | 404 |
| Emitted by | Signing page |
| Title values | Sealed document is not ready yet |
| Trigger | Signing page: sealed PDF not ready yet (ES-12 poll) |
What happened
A download of the sealed copy was requested before the seal job finished. The response is HTTP 404 with this slug rather than not-found, so clients can tell “not yet” from “never”.
What it means
Sealing runs as a job after the last signature: flattening, the certificate of completion page, and the cryptographic seal with its timestamp. It usually takes seconds.
What to do next
Poll with backoff, or subscribe to the document.sealed webhook event and download when it arrives. The signing page polls automatically.
Problem body
Every error is an RFC 9457 problem document with media type
application/problem+json. The type member is the
stable identifier to switch on; docs_url is this page.
{
"type": "/problems/not-ready",
"title": "Sealed document is not ready yet",
"status": 404,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/not-ready"
}