cron-retry
by jrbobbyhansen-pixel
Self-Hosted & AutomationBrief
Auto-retry failed cron jobs on connection recovery.
Description
What This Skill Does
Monitors cron jobs for network-related failures and retries them automatically when connectivity is restored. Works by adding a recovery check to the heartbeat cycle: on each heartbeat, it lists all jobs, filters for error states caused by transient network issues, and re-runs eligible ones. Skips logic errors, auth failures, and disabled jobs.
Distinguishes retryable network errors from permanent failures automatically, so jobs recover without manual inspection or re-triggering.
When to Use It
- Recovering a nightly briefing that failed to send during a network outage
- Retrying a scheduled data fetch after a DNS lookup failure
- Resuming a job that timed out mid-run due to dropped connectivity
- Auto-recovering message delivery failures after a server restart
- Reducing manual intervention when flaky network causes recurring cron failures
Example Workflow
User asks: My evening briefing cron job failed last night due to a network error — can it be recovered?
- 1
Call cron tool with action: "list" to fetch all jobs
- 2
Filter jobs where lastStatus is "error" and enabled is true
- 3
Check lastError of each failed job against network error patterns (ETIMEDOUT, fetch failed, ECONNREFUSED, etc.)
- 4
Call cron tool with action: "run" and the job ID for each retryable job
- 5
Report recovery results
Recovered 1 job: evening-wrap-briefing
Installation
clawhub install jrbobbyhansen-pixel/cron-retryRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.