Cancel an Unsigned QCDS Request

Cancel an unsigned Request when the signing transaction should stop permanently. Cancellation is a terminal Request action: QCDS closes active participant access and preserves the Request history rather than deleting the transaction.

Where Cancellation Is Available

Use the Cancel action from the Unsigned Requests list or Cancel Request from Request Details → Overview. The current frontend asks you to confirm the action before QCDS submits it.

Cancellation is allowed for an active Request in Scheduled, Sending, Delivery Failed, Sent, Delivered, Viewed, In Progress, Waiting, or Paused state. A completed or otherwise terminal Request does not use this unsigned cancellation path.

What Cancellation Changes

QCDS moves the Request to Cancelled, sets its terminal timestamp, and changes still-active participant records to Cancelled. The cancellation transition and reason are written to the Request Timeline and domain audit history.

QCDS then closes every participant's signer links/sessions so the cancelled transaction can no longer be completed through an old invitation.

Cancellation Notices Are Separate Delivery Results

After the Request is cancelled, QCDS attempts a cancellation email to each participant address using the Request's cancellation message/template context and participant language. Each address gets its own delivery record.

A cancellation email failure does not undo the cancellation. The Request remains Cancelled and signer access remains closed even if a recipient's mail server rejects the notice.

Delivery Is Idempotent and Preserved

QCDS deduplicates cancellation notices so an address already recorded as successfully sent is not needlessly sent again by the same cancellation-delivery process. Successful and failed notices are recorded independently, including Timeline events for cancellation notice sent or failed.

What Cancellation Does Not Do

Cancellation does not delete the immutable Request snapshot, prior invitation/delivery history, signer activity already recorded, or audit evidence. It closes the active signing workflow while retaining the historical record of what occurred before cancellation.

If your goal is only to remind a signer or correct an email problem, use the reminder or Delivery controls instead; cancellation is the stop-the-transaction action.

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.