Troubleshoot Scheduled Tasks, Notifications, and Updates

This article shows how to diagnose Lazy Scheduler/cron execution, bad task cadence, disabled or duplicate tasks, Joomla Mail delivery, notification retries, update-site state and package update permissions.

What you need to know

  • Transfer completion/failure events are persisted to a durable outbox and delivered through Joomla Mail by the 5-minute Notification Delivery task.
  • QCSB 1.01.08 does not expose a customer Email Templates tab. Internal responsive templates/delivery state are maintained by the service and upgrades preserve genuine stored customizations.
  • The canonical task cadences are: Entitlement Revalidation 60 minutes, Transfer Continuation 5 minutes, Recovery Vault Cleanup 60 minutes, and Notification Delivery 5 minutes.
  • QCSB is preservation-first: normal upgrades install the outer package over the current installation, and downgrade/uninstall behavior does not intentionally erase stored configuration/history merely because a feature is no longer usable.

Troubleshooting procedure

  1. Check Status for the specific task-integrity warning and last exit code.
  2. Open System → Scheduled Tasks and verify the canonical task exists exactly once, is published, and uses the required cadence.
  3. Confirm Joomla’s scheduler runner actually runs; on low-traffic sites prefer server cron over relying only on Lazy Scheduler.
  4. For notifications, also verify Joomla Mail; for updates, verify the QCSB update site and Extension Manager permission.
  5. Run the repaired task and confirm the next Status check is healthy.

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.

If it still fails

  • Change one variable at a time and repeat the same small test after each correction.
  • Use QCSB sanitized errors/Status/Test Connection before changing unrelated provider or Joomla settings.
  • If the issue remains, collect version, provider type, Workspace/user role, task state where relevant, and sanitized messages for support. Never include secrets.

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.