When You May Still Need a Real Cron Job

QCTNH can remove the need for a separate server cron on many sites, but some workloads and infrastructure requirements still call for real cron/CLI scheduling.

Use a real cron when

  • A required Scheduled Task is marked CLI-only. QCTNH intentionally excludes CLI-exclusive tasks from WebCron eligibility.
  • Your security policy does not allow a public WebCron endpoint, even with Joomla’s secret WebCron key.
  • The site is private/intranet-only or resolves only to private/reserved IP space, so the QuantaCade service cannot safely reach it.
  • You require infrastructure-controlled execution independent of external service availability.
  • You have long-running tasks whose operational design is better suited to Joomla CLI and server process supervision.

QCTNH and cron are not mutually exclusive

You can keep existing cron infrastructure while using QCTNH for health visibility. Avoid creating competing aggressive triggers unless you understand Joomla Scheduler locking, because multiple trigger sources can produce overlapping attempts even though Joomla’s locks are designed to protect actual execution.

Operational context

For When You May Still Need a Real Cron Job, keep the execution boundary clear: QCTNH prepares and observes Joomla’s own scheduler infrastructure, while the task routines remain owned by Joomla and the extensions that registered them. A healthy QCTNH installation therefore depends on a healthy Joomla Scheduler component and System - Schedule Runner plugin, not on a proprietary QCTNH task queue.

After any install, upgrade, or repair that touches scheduling, finish by opening Dashboard, running Check WebCron, and reviewing WebCron readiness, Scheduler Health, and Recent Activity. That verifies the local Joomla prerequisites before you involve the external service path.

Community Discussion

Want to compare scheduler workflows, share practical tips, or discuss how you use this QCTNH feature? Visit the QC Task Nudge & Health Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.