How Automatic Unsigned-Request Reminders Work

Automatic reminders are sent by the Joomla Scheduled Task named QC Digital Signature Automatic Reminders. The task checks active incomplete signers and uses the reminder interval frozen into each sent Request, so later workspace-setting changes do not rewrite that Request's reminder policy.

The Request Keeps Its Own Reminder Interval

When a Request is created, QCDS freezes its reminder policy into the immutable Request snapshot. The reminder interval is constrained to 1–30 days; the normal workspace default is 3 days.

The Scheduled Task may run much more frequently than the reminder interval. Its job is to check whether a reminder is due, not to send every time it runs.

Who Is Eligible

Automatic reminder processing considers Requests that have already been sent and are in active unsigned lifecycle states such as Sent, Delivered, Viewed, In Progress, or Waiting. The Request must have a sent timestamp and must not be past its deadline.

For each participant, the routing stage must currently be active, and the participant must not already be completed, declined, cancelled, revoked, or replaced. This prevents a later sequential signer from being reminded before their turn.

How QCDS Decides a Reminder Is Due

For the participant, QCDS finds the most recent successful invitation, invitation resend/replacement, or reminder. If that successful delivery occurred within the Request's frozen reminder interval, the participant is skipped for the current task run.

Once the interval has elapsed, QCDS queues a signer reminder for the active participant and attempts delivery. Successful and failed attempts are recorded in the Request Timeline.

Scheduled Task Cadence

A fresh QCDS installation creates the canonical Automatic Reminders task with an hourly schedule. Existing administrator-selected schedules are preserved during updates; QCDS does not overwrite an existing task's chosen schedule just to restore the default.

The QCDS Status area expects the Scheduled Tasks plugin to be enabled and exactly one published Automatic Reminders task to exist. It shows the task's last execution, last exit code, and next execution.

Delivery Failures

A mail failure is not treated as a successful reminder. QCDS records the failure and the delivery subsystem can place the delivery into retry handling with bounded backoff. Check the Request Timeline/Delivery history and Joomla Scheduled Tasks health when reminders appear overdue.

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.