Cisco Cloud Observability Kubernetes and App Service Monitoring Kubernetes Events Collection Events Reason Reference Current: CronJob Event Reasons PDF Download PDF Download page CronJob Event Reasons. Current page All pages CronJob Event Reasons This page includes the reference list for the cronjob event reasons that Kubernetes® uses in Version v1.21.3.Warning Event TypeEvent ReasonMessageUnexpectedJobSaw a job that the controller did not create or forgot.FailedNeedsStartCannot determine if job needs to be started: %errMissScheduleMissed scheduled time to start a job: %{time}FailedGetGet job: %{error from api-server}FailedCreateError creating job.FailedDeleteDeleted job: %{error from api-server}UnParseableCronJobScheduleUnparseable schedule for cronjob: %{schedule}InvalidScheduleInvalid schedule schedule: %{schedule} : %{err}UnparseableScheduleUnparseable schedule for cronjob: %{schedule}TooManyMissedTimesToo many missed start times: %{number of misses}. Set or decrease .spec.startingDeadlineSeconds or check clock skew.Normal Event TypeEvent ReasonMessageSawCompletedJobSaw completed job: %{name}, status: %vMissingJobActive job went missing: %{job-name}SuccessfulCreateCreated job %{job name}.SuccessfulDeleteDeleted job: %{job name}.JobAlreadyActiveNot starting job because prior execution is running and concurrency policy is Forbid.OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®. ×