Joomla Lazy Scheduler vs Server Cron for QCSB
This article explains that Joomla Lazy Scheduler can run tasks from site traffic but a server cron/CLI runner is more reliable for low-traffic sites and time-sensitive transfer continuation.
What you need to know
- The canonical task cadences are: Entitlement Revalidation 60 minutes, Transfer Continuation 5 minutes, Recovery Vault Cleanup 60 minutes, and Notification Delivery 5 minutes.
Choose the runner
| Runner | Operational effect |
|---|---|
| Joomla Lazy Scheduler | Tasks are triggered by site traffic. Useful on active sites, but runs can be late when the site is quiet. |
| Server cron / CLI scheduler runner | Runs Joomla Scheduled Tasks independently of frontend traffic. Preferred for dependable 5-minute transfer/notification work and hourly entitlement/recovery maintenance. |
Recommended production setup
- Open QCSB Status and use the scheduler guidance to identify the server-specific Joomla scheduler command.
- Configure the host/server cron to run Joomla Scheduled Tasks reliably (commonly the Joomla scheduler runner with --all).
- Keep the individual QCSB task schedules at their canonical 60/5/60/5-minute intervals.
- Confirm recent execution/exit state in Joomla Scheduled Tasks and QCSB Status.
- On a quiet site, do not interpret a published task as healthy until an actual runner is executing it.
Verify the result
- Status shows the canonical task as healthy and published.
- The cadence matches the current required interval.
- A manual/next scheduled run finishes without a repeated non-zero exit state.
Troubleshooting
- On a quiet site, use server cron for Joomla scheduler:run --all rather than assuming Lazy Scheduler will run on time.
Community Discussion
For practical QCSB workflows and discussion with other Joomla site owners, visit the QC Storage Bridge Community. For private support, bug reports, account-specific entitlement issues, or feature requests, use the QuantaCade support system.