Kubernetes / Deployments, Scheduling & Batch Workloads
Investigate a Kubernetes CronJob that missed its expected run
A missed execution can involve suspension, scheduling deadlines, controller availability or timezone assumptions. Inspect the actual controller state.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app describe cronjob nightlyRead the result
The description shows schedule, suspension and recent activity. Retained history may omit older runs and does not prove exactly-once execution.
Resolve and verify
Compare schedule interpretation, deadline and controller evidence with the intended business time. Correct the demonstrated setting and verify the next expected run.
Before changing production
Do not launch a compensating job before checking whether a late or duplicate run already completed the business work.