Cancel an Unsigned QCDS Request

Cancel an active Request, close further signing, notify signers where applicable, preserve its historical record, and understand why cancellation is different from deletion.

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

  1. Open the unsigned Request or use its Cancel action.
  2. Review that you are cancelling the intended transaction.
  3. Confirm the cancellation.
  4. Verify signing access is closed and cancellation communication is delivered as applicable.
  5. Retain the Request history; cancellation is a lifecycle event, not deletion of delivery/view/evidence records.

Cancel an active Request

The key point for Cancel an Unsigned QCDS Request is Cancel an active Request. Work from the current QCDS 2.0.7 interface and the saved state of the specific workspace, Template, Request, or installation involved. QCDS separates reusable configuration from sent transaction evidence, so prefer the action that changes only the intended current object rather than rewriting unrelated historical records.

For Cancel an Unsigned QCDS Request, 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.

Close further signing

The key point for Cancel an Unsigned QCDS Request is close further signing. Work from the current QCDS 2.0.7 interface and the saved state of the specific workspace, Template, Request, or installation involved. QCDS separates reusable configuration from sent transaction evidence, so prefer the action that changes only the intended current object rather than rewriting unrelated historical records.

For Cancel an Unsigned QCDS Request, 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.

Notify signers where applicable

The key point for Cancel an Unsigned QCDS Request is notify signers where applicable. Work from the current QCDS 2.0.7 interface and the saved state of the specific workspace, Template, Request, or installation involved. QCDS separates reusable configuration from sent transaction evidence, so prefer the action that changes only the intended current object rather than rewriting unrelated historical records.

Preserve its historical record

The key point for Cancel an Unsigned QCDS Request is preserve its historical record. Work from the current QCDS 2.0.7 interface and the saved state of the specific workspace, Template, Request, or installation involved. QCDS separates reusable configuration from sent transaction evidence, so prefer the action that changes only the intended current object rather than rewriting unrelated historical records.

And understand why cancellation is different from deletion

The key point for Cancel an Unsigned QCDS Request is and understand why cancellation is different from deletion. Work from the current QCDS 2.0.7 interface and the saved state of the specific workspace, Template, Request, or installation involved. QCDS separates reusable configuration from sent transaction evidence, so prefer the action that changes only the intended current object rather than rewriting unrelated historical records.

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 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.