Retry Failed QCFUM Email and Troubleshoot Joomla Mail Delivery

QCFUM Pro, Max, and All Access can use Retry Now for a Queued or Failed email when the Email retry setting is enabled. Retry Now performs one immediate send attempt using the stored template key, recipient, and encrypted workflow tokens.

Email retry does not repair the underlying mail configuration. Use the queue error and a controlled test message to fix Joomla mail or template problems before repeatedly retrying.

Use Retry Now

  1. Open QCFUM Administrator → Email.
  2. Review the Email Delivery Queue and read Last Error.
  3. Confirm the template still exists and is published.
  4. Confirm Pro+ entitlement and the Email retry setting are active.
  5. Fix Joomla mail or template configuration if needed.
  6. Choose Retry Now on a Queued or Failed row and review the updated state.

Retry Now Is Different from Scheduled Retry

Retry Now increments the row’s attempt count and performs one send immediately. Success marks the row Sent. Failure marks it Failed and clears Next Attempt. The configured maximum-attempt rule belongs to the scheduled queue processor; Retry Now itself does not schedule another automatic hour-later attempt.

Why Retry Now Can Refuse the Request

The server requires Pro+ email_queue_retry and automation_email_retry_enabled=1. The Email table may still render the button based on the Pro+ feature gate, so a site with the retry setting switched off can see Retry Now but receive the server-side “must be enabled under Scheduled Automation” refusal.

Troubleshooting Checklist

  • Use Send Test on the relevant template and verify Joomla Global Configuration mail settings and the site’s mail transport.
  • Confirm the template is published. An unpublished template cannot be rendered for a retry.
  • Review Last Error for SMTP/transport details rather than assuming the recipient address is the only problem.
  • If the error says queued data cannot be decrypted, verify whether the Joomla site secret changed after the row was queued.
  • Confirm the stored recipient is still the address that should receive this historical delivery.
  • If automatic retries are expected, confirm commercial Scheduled Automation is enabled and its Joomla task is actually running.

Security Boundary

QCFUM does not expose queued token payloads in the administrator table. Keep queue troubleshooting focused on recipient, template, status, attempts, timing, and errors rather than attempting to recover secure invitation or password values.

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.