QC Update Laboratory Production Safety Check

QC Update Laboratory Production Safety Check periodically re-evaluates tested update records against the current live site so QCUL can record whether an exact production push still appears safe to offer.

Default schedule

Every 24 hours. The canonical task type is qc_update_lab.approval_validity even though the user-facing title is Production Safety Check.

What it rechecks conceptually

• Current production starting version/target context.
• Availability/integrity of the tested package.
• Production identity/readiness signals attached to retained tested items.

It never pushes automatically

The task can update readiness/safety evidence, but production installation still requires the administrator’s explicit Push to Production action, Super User authorization, current readiness checks, and protection choice.

Verify task execution

In System → Scheduled Tasks, inspect this task’s enabled state, Last Execution, Next Execution, and Last Exit Code. If the row exists but never runs, repair Joomla’s scheduler trigger (Lazy Scheduler/server cron); recreating the QCUL task will not solve a scheduler that is never invoked.

Scheduled-task verification

After changing or repairing QC Update Laboratory Production Safety Check, verify the canonical task row in System → Scheduled Tasks: enabled/disabled state, Last Execution, Next Execution, and Last Exit Code. Registration alone does not prove the maintenance routine runs; Joomla Scheduler still needs Lazy Scheduler or server cron to trigger due work.

Community Discussion

Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.