SignEnvoy docs
Sign in Start in the sandbox

Error reference Your copy isn't ready yet

Error reference

Your copy isn't ready yet

A cc recipient's link was opened before the document was complete.

Problem type /problems/copy-not-ready
HTTP status 409
Emitted by Signing page
Title values
Your copy isn't ready yet
Trigger
Signing page: a cc's link opened before the document is complete (D179(c), ADR 0077); the copy is mailed at the seal, so nothing is requestable

What happened

A recipient with the role cc opened their link while the document was still out for signing. The response is HTTP 409, and the page tells them their copy isn’t ready yet.

What it means

A cc only receives a copy. It gets no link while the document is in flight: its one email, with its first link, is sent when the document is sealed, and that link opens the final copy. A link opened before then can only be one issued before this rule existed. Nothing about the document has changed, and nobody else is affected.

What to do next

For a recipient: nothing. The link to the final copy arrives by email once everyone has signed or approved. For a sender: nothing either; a cc cannot be given a signing link (POST /v1/documents/{doc_id}/recipients/{recipient_id}/signing-link answers invalid-state). If the person has to act on the document, make them a signer, approver or viewer instead. On a document sent with delivery: "none", no copy is emailed: send the final copy yourself from GET /v1/documents/{doc_id}/download.

Problem body

Every error the API returns 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/copy-not-ready",
  "title": "Your copy isn't ready yet",
  "status": 409,
  "instance": "/v1/...",
  "docs_url": "https://staging.signenvoy-docs-b4g.pages.dev/errors/copy-not-ready"
}