<p>I have a cluster that includes a Cronjob scheduled to run every 5 minutes.</p>
<p>We recently experienced an issue that incurred downtime and required manual recovery of the cluster. Although now healthy again, this particular cronjob is failing to run with the following error:</p>
<pre><code>Cannot determine if job needs to be started: Too many missed start time (&gt; 100). Set or decrease .spec.startingDeadlineSeconds or check clock skew.
</code></pre>
<p>I understand that the Cronjob has 'missed' a number of scheduled jobs while the cluster was down, and this has past a threshold at which no further jobs will be scheduled.</p>
<p>How can I reset the number of missed start times and have these jobs scheduled again (without scheduling <strong>all</strong> the missed jobs to suddenly run?)</p>

<p>Per the <a href="https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/" rel="noreferrer">kubernetes Cronjob docs</a>, there does not seem to be a way to cleanly resolve this. Setting the <code>.spec.startingDeadlineSeconds</code> value to a large number will re-schedule <strong>all</strong> missed occurrences that fall within the increased window.</p>
<p>My solution was just to <code>kubectl delete cronjob x-y-z</code> and recreate it, which worked as desired.</p>
