cron-jobs-stalled

To recover a stalled cron job, this Skill reads the jobs.json file to identify stopped jobs where next_run_at is null and applies a targeted fix for scheduler bugs or script quality issues.

A cron job has a null next_run_at value when it has stopped running due to underlying scheduler bugs or script quality issues, requiring a diagnostic check of the jobs.json file to determine the root cause.

The best way to fix a cron job that stopped running is to apply a 60-second recovery patch after diagnosing whether the failure stems from a scheduler bug or a script error in the jobs.json configuration.

Yes, you need filesystem access to the cron jobs directory because this Skill uses Python libraries like pathlib and subprocess to read the jobs.json file and execute the necessary recovery commands.

Yes, this Skill leverages Python's subprocess module alongside json and pathlib to inspect the jobs.json file and execute the appropriate 60-second recovery patch for the stuck cron job.

This diagnostic process identifies specific cron job errors including scheduler bugs that halt execution and script quality issues that cause failures, applying tailored recovery solutions based on the detected root cause.