How QCDS Request Expiration and Deadlines Work

Request expiration values, workspace defaults, time-zone handling, Timing and Deadlines task processing, and the signer/sender behavior after a request is no longer active.

This guide applies to All plans; sender and administrator 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 QCDS > Requests and locate the exact transaction.
  2. Open Request Details and inspect status, participant progress, Timeline, and delivery history.
  3. Use the narrow supported action described in this guide rather than recreating the whole Request.
  4. Confirm the new delivery/lifecycle event is recorded.
  5. Verify successful signer links, completed artifacts, and older history remain intact.

Request expiration values

Request expiration is transaction-specific and is interpreted through the QCDS timing workflow using UTC as the authoritative backend time. The Request Timing and Deadlines Scheduled Task advances due expiration/deadline work. Workspace defaults seed new Requests, but the sender can choose an appropriate expiration for the individual transaction before Send Now.

For How QCDS Request Expiration and Deadlines Work, 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.

Workspace defaults

Request expiration is transaction-specific and is interpreted through the QCDS timing workflow using UTC as the authoritative backend time. The Request Timing and Deadlines Scheduled Task advances due expiration/deadline work. Workspace defaults seed new Requests, but the sender can choose an appropriate expiration for the individual transaction before Send Now.

For How QCDS Request Expiration and Deadlines Work, 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.

Time-zone handling

Request expiration is transaction-specific and is interpreted through the QCDS timing workflow using UTC as the authoritative backend time. The Request Timing and Deadlines Scheduled Task advances due expiration/deadline work. Workspace defaults seed new Requests, but the sender can choose an appropriate expiration for the individual transaction before Send Now.

Timing and Deadlines task processing

Request expiration is transaction-specific and is interpreted through the QCDS timing workflow using UTC as the authoritative backend time. The Request Timing and Deadlines Scheduled Task advances due expiration/deadline work. Workspace defaults seed new Requests, but the sender can choose an appropriate expiration for the individual transaction before Send Now.

And the signer/sender behavior after a request is no longer active

Request expiration is transaction-specific and is interpreted through the QCDS timing workflow using UTC as the authoritative backend time. The Request Timing and Deadlines Scheduled Task advances due expiration/deadline work. Workspace defaults seed new Requests, but the sender can choose an appropriate expiration for the individual transaction before Send Now.

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.
  • Joomla Scheduled Tasks shows the relevant canonical QCDS task enabled with a sensible next execution time.
  • 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.