QCDS Request and Delivery Statuses Explained

Plain-language reference for common request states, signer progress states, invitation/completion delivery states, completion_failed, archived status, and what each state implies for available actions.

This guide applies to All plans; sender and follows the accepted QC Digital Signature 2.0.7 implementation. Where older walkthrough language differs from the current interface or source behavior, use the current QCDS state as the authority.

Before You Begin

Open Requests and work from the actual Request Details instead of recreating a transaction when one delivery address or reminder needs attention.
Separate document/signing status from email-delivery status. A valid signer link or Completed PDF can remain valid even when a particular email delivery failed.
Preserve the Request history when correcting addresses, retrying delivery, cancelling, or archiving.

Step-by-Step Workflow

Open the QCDS screen or record that owns the topic so you are reading the current state rather than an old screenshot or memory.
Compare the visible state with the current 2.0.7 rules described in this guide.
Identify whether the value belongs to global installation settings, one sender workspace, a reusable Template, or one immutable/sent Request.
Make changes only at the layer that owns the behavior.
Verify the result with a safe test and preserve historical Requests/evidence.

Request Statuses You Will Commonly See

Sending: QCDS is creating or attempting the initial delivery work.
Sent: the applicable invitation deliveries succeeded.
Sent with errors: at least one invitation succeeded and at least one address needs attention; successful signer links remain valid.
Not sent / Undeliverable: no intended invitation delivery succeeded; correct the address or mail problem and retry the narrow delivery.
Viewed / In progress: a signer opened the secure page and/or started completing fields.
Completion failed: required signing may already be finished, but QCDS must recover/finalize the Completed PDF; do not ask signers to sign again.
Completed: required signing finished and the completed artifact is available.
Completed - Archived: the completed transaction was filed in Archived; its document and evidence remain available.

Delivery Status Is a Separate Layer

An individual delivery can be Pending, Sending, Sent, retryable after a failure, Undeliverable, or stopped/replaced after an address correction. Read these delivery states alongside the Request lifecycle so you do not cancel a valid transaction merely because one mailbox rejected one message.

Plain-language reference for common request states

Participant language is resolved at use time in this order: Contact Preferred Language, sender/workspace Default frontend language, administrator Default frontend language, then English (en-GB). QCDS can translate creator-authored participant communication when needed, while protecting tokens, URLs, and HTML. If safe translation is unavailable, it falls back to the complete frozen source message rather than sending a partially translated mixture.

For QCDS Request and Delivery Statuses Explained, verify this behavior using the actual object involved rather than a generic assumption. A global administrator setting, a sender-workspace preference, a reusable Template, and a sent Request have different ownership and history rules. QCDS is intentionally designed so changes for future work do not silently rewrite the evidence of an already-sent transaction.

Signer progress states

Invitation/completion delivery states

Completion_failed

Archived status

How This Fits into the QCDS Workflow

Request management is designed to repair the narrow failed step while preserving successful signer links and historical evidence. Delivery errors, reminders, cancellation, completion, and archival are lifecycle actions on one transaction—not reasons to overwrite its record.

QCDS records lifecycle and delivery events so a repair can be visible rather than silently replacing what happened. That is especially important for address corrections, retries, cancellation, reminders, and completed-document resends.

Verify the Result

Request Details shows the expected lifecycle, participant, Timeline, and delivery state after the action.
A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

Cancelling/recreating an otherwise valid Request just to repair one failed email address.
Leaving transient unsent work and expecting it to appear later as a persistent draft Request.

Troubleshooting

If due work is late, confirm the canonical task is enabled and being triggered; a correctly defined task on a quiet Joomla site can still remain overdue without a reliable wake-up mechanism.
If the Request is partly successful, preserve it and repair the failed participant/delivery step. Successful links and recorded history should remain usable.

Operational Best Practice

Test meaningful changes with controlled data before relying on them in production. Keep QCDS, Joomla mail, Scheduled Tasks, and entitlement health observable; preserve successful Requests and completed evidence; and make the smallest change that solves the actual problem. For handoff or support, record the QCDS version, relevant Request/Template reference, the exact action taken, and the visible result without including secrets.

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.