Understand the QCFUM Email Delivery Queue
QCFUM keeps a delivery queue for eligible email attempts that reached Joomla mail and failed. The queue is a recovery record, not the normal path for every outgoing message.
In QCFUM 2.0.4, automatic queueing requires Pro or higher and the Email retry Scheduled Automation setting. Missing or unpublished templates fail before Joomla mail is attempted, so those failures do not create queue rows.
When a Failed Email Is Queued
When a published template renders, Joomla mail fails, and retry is available, QCFUM stores a row with status Queued, records the original failure as attempt 1, and schedules the next attempt one hour later. The recipient, template key, error, timestamps, and retry state are retained.
Sensitive Token Context Is Encrypted
Queue token data is encrypted with AES-256-GCM using a key derived from the Joomla site secret. New queue rows therefore do not store workflow token data as readable JSON. Legacy pre-1.0.5 rows can still be read. If the Joomla secret changes, encrypted queue data may no longer decrypt and the retry will fail with a specific queue-decryption error.
What the Email Tab Shows
The Email tab displays the newest 50 queue rows with recipient, template, status, attempts, last error, next attempt, and Retry Now. Separate counters show total Queued, Failed, and Sent records across the queue table.
Scheduled Retry Behavior
| State | 2.0.4 behavior |
|---|---|
| Queued | Due rows are processed oldest first, up to 50 per Scheduled Automation run. |
| Retry fails below max | Attempts increase; status remains Queued; next attempt is one hour later. |
| Retry reaches max | Status becomes Failed; next attempt is cleared; QCFUM attempts the final-failure administrator notice. |
| Retry succeeds | Status becomes Sent; sent time is recorded; error and next-attempt fields are cleared. |
Why Sent and Failed Rows Remain
QCFUM retains completed queue rows as delivery evidence. A Failed row can still be retried manually when Pro+ retry is available; Sent rows remain read-only history.
Community Discussion
Want to compare Joomla user-management workflows, share practical QCFUM tips, or discuss how other administrators use this feature? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.