QC Live Forum Notification Delivery Scheduled Task

QC Live Forum Notification Delivery is registered as qc_forum.notifications and defaults to every five minutes. The routine first reconciles persisted live-session notification events, then processes due email recipients through the current QCLF template and recipient-validation pipeline.

On-site and email state share notification records but are separate delivery channels; email retries do not turn the on-site notification center into a mail queue.

Live Reminder/Event Reconciliation

Each delivery run calls reconcileLiveNotifications(). That reconciler can queue Live Scheduled, Rescheduled, Starting Soon reminders, Live Now, Cancelled, Archive Ready, stale/failure, and archive-failure events from the persisted live-session state. Obsolete future Starting Soon reminders are cancelled when the schedule signature changes.

Due Email Processing

  • The task processes up to 100 due notification recipients per normal service call (the service hard-bounds a supplied limit to 1–500).
  • It revalidates the Joomla account, global email preferences, reaction-email preference, subscription/recipient relationship, content access, administrator recipient configuration, and published matching templates before sending.
  • Each notification+template pair maintains independent state. A template that already sent successfully is not re-sent because another matching template still needs retry.
  • Email delivery has a three-attempt ceiling; exhausted failures and a queue stalled for more than 30 minutes can emit operational notification events.

On-Site Notice Timing

When an event is emitted for an on-site-enabled user, the notification row carries separate onsite_state plus any scheduled_for time. The frontend Notification center exposes due on-site rows and revalidates current access/relationships. The email task does not need to “send” an on-site notice through Joomla Mail.

Troubleshoot Delivery in Layers

  1. Confirm the Notification Delivery task is actually executing.
  2. Check whether the expected notification event/recipient row exists and is due.
  3. Check current recipient relationship/preferences/access before blaming the template.
  4. Check published matching templates and unresolved-token state.
  5. Finally check Joomla Mail transport for email-specific failure.

Community Discussion

Want to compare forum workflows, share practical QCLF tips, or discuss how other Joomla site owners use this feature? Visit the QC Live Forum Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.