Resend the Exact Completed Document to Original Parties

Use Resend when the completed transaction is correct and you simply need to deliver the completed document again. QCDS resends the exact stored verified PDF bytes; it does not re-run signing or silently regenerate a different completed artifact.

Where Resend Is Available

A completed Request can be resent from the Completed or Archived Request list, and Request Details also provides Resend Completed Document for completed Requests with a verified artifact.

QCDS refuses the resend if the Request is not completed or if the verified completed PDF artifact is unavailable.

Who Receives the Resend

For current Requests, QCDS starts from the active original completion/replacement delivery records. It excludes rows that were superseded by an address correction or Stop Trying, deduplicates the remaining valid email addresses, and creates a new resend delivery row for each recipient.

This means a prior approved address correction is honored. QCDS does not revive an address that was explicitly superseded or stopped just because you resend the completed document.

The Completed PDF Is Verified Before Email

QCDS attaches the completed PDF itself to the email. Before attachment, it checks the stored artifact's provider, PDF MIME type, file readability, size, and SHA-256 hash against the completed artifact record. A regenerated or temporary substitute is not accepted for this delivery path.

Resend Has Its Own Email Wording

Resend deliveries use the Request's frozen Request Resent email source when available, rather than pretending this is the original completion delivery. The completed PDF attachment remains the authoritative document delivery; QCDS does not depend on a later-expiring browser download link in the email.

History Is Append-Only

Resending does not rewrite the original completion-delivery rows. QCDS adds new resend rows and records the resend request and each delivery result in Timeline/audit history. If one or more recipients fail, the successful deliveries remain successful and the failed resend rows remain available for troubleshooting/retry.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.