Troubleshoot QCFUM Email Templates, Queue, and Delivery

Email troubleshooting in QCFUM should follow the delivery path in order: template availability, recipient and tokens, Joomla mail transport, then the retry queue. The queue is not a substitute for a missing or unpublished template.

QCFUM only queues an eligible delivery after an actual Joomla-mail failure when Pro+ email retry is available and enabled. Queue token data is protected with AES-256-GCM using the Joomla site secret.

Check the Template Before the Queue

  1. Confirm the workflow is using the expected template key.
  2. Confirm the template exists and is published. Normal runtime delivery fails before Joomla mail if the template is missing or unpublished.
  3. Confirm the recipient address is valid and the workflow actually has a recipient.
  4. Check the subject/plain text and, on Pro+, Custom HTML. Plain text remains required.
  5. Check tokens against the real workflow. The editor palette and Send Test sample data are broader than the tokens every workflow supplies.

Use Send Test Carefully

Send Test is useful for Joomla mail transport and template rendering, but it can test a template directly by ID even when that template is unpublished. A successful test therefore does not prove the live workflow can select the template. Also inspect unresolved-token warnings rather than assuming a successful test proves every workflow token is populated.

Read Queue State and Error Data

The Email Delivery Queue records Queued, Sent, and Failed status plus attempts, last error, next attempt, and sent time. Scheduled retry processes due Queued rows when Pro+ retry is available. The maximum automatic attempts comes from Scheduled Automation. Retry Now is one immediate attempt and requires the same Pro+ retry capability.

Watch for Joomla-Secret Changes

Queued token data is encrypted from the Joomla configuration secret. If that secret changes after a row was queued, QCFUM cannot decrypt the stored workflow data; the row records a decryption failure instead of sending with corrupted tokens.

Do Not Reconstruct Secure Values Manually

If the failed message contained an Invite Link or temporary password, regenerate or resend it through the supported QCFUM workflow. Do not copy token hashes, queue ciphertext, or passwords from database records into a manual email. Invite nudge/resend logic intentionally rotates or stages secure tokens so the delivered link remains controlled.

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.