After maintenance, a utility-billing CronJob still has suspend: tru…

Question

After maintenance, a utility-billing CronJob still has suspend: true and no new Jobs appear. What should the team do?

Accepted Answer

Set suspend back to false so the CronJob can create Jobs again on its schedule — suspend: true is the pause button on the alarm clock—the CronJob object is still there, it just will not create new Jobs. Flip suspend to false and the schedule starts ringing again.

Answer

Delete the namespace to clear suspended CronJob state across the cluster

Answer

Convert the CronJob into a DaemonSet so schedules are evaluated on every node

Answer

Raise the startingDeadlineSeconds to zero to force an immediate historical catch-up run

After maintenance, a utility-billing CronJob still has suspend: true and no new Jobs appear. What should the team do?

Short Explanation

Full Explanation