Use the QCDS Request Timeline and Delivery History

QCDS separates chronological transaction history from actionable email-delivery records. Use Timeline to understand what happened and when; use Delivery to inspect each invitation or completed-document email address and fix delivery problems.

Timeline: Read the Request Chronologically

Open Request Details and select Timeline. QCDS presents a readable history with the event label, summary, timestamp, and—when available—the related participant or actor.

Current friendly labels include Request prepared, Request sent, Request sent with email errors, Invitation sent/failed, Email address corrected, Invitation retry requested, Delivery attempts stopped, Reminder sent/failed, Request viewed, Signer completed, Request completed, Completed request archived, Completed document emailed/failed, Completion email address corrected, Completed document resent, and Request cancelled.

Timeline is the right place to reconstruct sequence. It is not a replacement for the Delivery table's per-address controls.

Delivery: Invitation Emails

The Delivery section lists each invitation address with its delivery status, attempt count, last attempt, signer-link state, any issue, and available actions. Link state can show Active, Completed, Closed, or Not issued; when available QCDS also shows the last-opened time.

A successful invitation remains usable even when another address for the same Contact fails.

Correct, Retry, or Stop an Invitation Address

For eligible Contact-backed failed/pending addresses, Correct & Send records the corrected address and sends a replacement. Failed/retry rows can expose Retry. Pending/retry/failed/sending rows can expose Stop Trying.

Stopping attempts or replacing an address does not erase the old delivery evidence. The historical row remains represented as stopped/replaced.

Completed-Document Email History

After completion, Delivery also shows Completed-document emails. The completed PDF remains valid and downloadable even if one or every completion email fails.

Eligible completion rows support the same operational pattern: correct a Contact email and send the exact completed PDF, retry a failed address, or stop further attempts. QCDS preserves the completed artifact and delivery history regardless of those mail outcomes.

Read Technical Errors Only When Needed

QCDS first translates common mail failures into a plain-language explanation—for example, a rejected mailbox/domain, Joomla mail authentication failure, connection timeout, or internal data/update problem. Expand Error details only when you need the underlying technical message for troubleshooting or support.

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.