[{"data":1,"prerenderedAt":16},["ShallowReactive",2],{"blog-tag-en-concurrencypolicy":3},[4],{"path":5,"title":6,"description":7,"date":8,"tags":9},"\u002Fblog\u002Fen\u002Fk3s-cronjob-silent-failure-concurrencypolicy-missed-schedule","The CronJob Stayed Green. It Hadn't Run in 24 Days. 4 Traps Behind K3s's Silent Scheduling Failures","K3s and Kubernetes CronJobs can keep showing 'Succeeded' while quietly not running for weeks. Here's how concurrencyPolicy, startingDeadlineSeconds, the 100-missed-schedule limit, and exit code 0 combine to create silent failures, and how to monitor for it.","2026-09-16",[10,11,12,13,14,15],"k3s","kubernetes","cronjob","concurrencypolicy","monitoring","sre",1792592705351]