Retry or Stop Trying a Failed Signer Email Delivery

Use Retry for retryable/failed deliveries, Stop Trying for a bad address that should no longer be attempted, and preserve delivery evidence in either case.

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

Retry for retryable/failed deliveries

QCDS sends through Joomla mail. A QCDS-specific sender name/email can override the identity used by QCDS, while Joomla remains the underlying transport. When a message fails, first separate identity/rendering problems from SMTP or receiving-server failures. A delivery error should not be treated as proof that the Request, secure link, or completed document is invalid.

For Retry or Stop Trying a Failed Signer Email Delivery, 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.

Stop Trying for a bad address that should no longer be attempted

QCDS sends through Joomla mail. A QCDS-specific sender name/email can override the identity used by QCDS, while Joomla remains the underlying transport. When a message fails, first separate identity/rendering problems from SMTP or receiving-server failures. A delivery error should not be treated as proof that the Request, secure link, or completed document is invalid.

For Retry or Stop Trying a Failed Signer Email Delivery, 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.

And preserve delivery evidence in either case

QCDS sends through Joomla mail. A QCDS-specific sender name/email can override the identity used by QCDS, while Joomla remains the underlying transport. When a message fails, first separate identity/rendering problems from SMTP or receiving-server failures. A delivery error should not be treated as proof that the Request, secure link, or completed document is invalid.

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.
  • 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 QCDS message content before confirming Joomla itself can send mail.
  • Editing the characters inside a supported token or translating the token name.
  • Asking signers to sign again when only final PDF generation or completion delivery failed.

Troubleshooting

  • If the email does not arrive, test Joomla mail, check QCDS delivery history, then distinguish authentication/connection problems from a rejected recipient address.

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.