How Automatic Unsigned-Request Reminders Work

Relationship between workspace reminder interval, frozen request policy, Signer Reminder Email Template, Scheduled Task cadence, due signer state, and manual reminders.

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.

Relationship between workspace reminder interval

QCDS relies on Joomla Scheduled Tasks for unattended work. The customer-facing canonical set is Automatic Reminders, Request Timing and Deadlines, Final PDF and Completion Delivery, and Entitlement Revalidation. Their normal cadences are 60 minutes, 5 minutes, 5 minutes, and 60 minutes respectively. Internal worker methods may exist in the package, but they are not extra tasks administrators should manually create. On a quiet site, a healthy task definition still needs Joomla to be triggered; use QC Task Nudge & Health or another reliable Joomla-native wake-up strategy when normal traffic is too sparse.

For How Automatic Unsigned-Request Reminders 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.

Frozen request policy

QCDS relies on Joomla Scheduled Tasks for unattended work. The customer-facing canonical set is Automatic Reminders, Request Timing and Deadlines, Final PDF and Completion Delivery, and Entitlement Revalidation. Their normal cadences are 60 minutes, 5 minutes, 5 minutes, and 60 minutes respectively. Internal worker methods may exist in the package, but they are not extra tasks administrators should manually create. On a quiet site, a healthy task definition still needs Joomla to be triggered; use QC Task Nudge & Health or another reliable Joomla-native wake-up strategy when normal traffic is too sparse.

For How Automatic Unsigned-Request Reminders 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.

Signer Reminder Email Template

QCDS relies on Joomla Scheduled Tasks for unattended work. The customer-facing canonical set is Automatic Reminders, Request Timing and Deadlines, Final PDF and Completion Delivery, and Entitlement Revalidation. Their normal cadences are 60 minutes, 5 minutes, 5 minutes, and 60 minutes respectively. Internal worker methods may exist in the package, but they are not extra tasks administrators should manually create. On a quiet site, a healthy task definition still needs Joomla to be triggered; use QC Task Nudge & Health or another reliable Joomla-native wake-up strategy when normal traffic is too sparse.

Scheduled Task cadence

QCDS relies on Joomla Scheduled Tasks for unattended work. The customer-facing canonical set is Automatic Reminders, Request Timing and Deadlines, Final PDF and Completion Delivery, and Entitlement Revalidation. Their normal cadences are 60 minutes, 5 minutes, 5 minutes, and 60 minutes respectively. Internal worker methods may exist in the package, but they are not extra tasks administrators should manually create. On a quiet site, a healthy task definition still needs Joomla to be triggered; use QC Task Nudge & Health or another reliable Joomla-native wake-up strategy when normal traffic is too sparse.

Due signer state

QCDS relies on Joomla Scheduled Tasks for unattended work. The customer-facing canonical set is Automatic Reminders, Request Timing and Deadlines, Final PDF and Completion Delivery, and Entitlement Revalidation. Their normal cadences are 60 minutes, 5 minutes, 5 minutes, and 60 minutes respectively. Internal worker methods may exist in the package, but they are not extra tasks administrators should manually create. On a quiet site, a healthy task definition still needs Joomla to be triggered; use QC Task Nudge & Health or another reliable Joomla-native wake-up strategy when normal traffic is too sparse.

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

  • A real test message leaves Joomla and arrives at the intended mailbox with the correct sender identity and format.
  • The Template validates and a new test Request renders the expected field/content behavior without changing older Requests.
  • 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

  • Publishing before running Validate and resolving actual configuration problems.
  • Assuming a later Template edit will update a Request that was already sent.
  • 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 QCDS message content before confirming Joomla itself can send mail.

Troubleshooting

  • If the email does not arrive, test Joomla mail, check QCDS delivery history, then distinguish authentication/connection problems from a rejected recipient address.
  • If the PDF preview or completed artifact fails, reproduce with a small known-good PDF and check QCDS Status/Scheduled Task health before changing field data.
  • 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.