Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Auto-retry failed cron jobs on connection recovery. Use when cron jobs fail due to network errors and should be retried when connectivity is restored. Integrates with heartbeat to detect failed jobs and re-run them automatically.
Auto-retry failed cron jobs on connection recovery. Use when cron jobs fail due to network errors and should be retried when connectivity is restored. Integrates with heartbeat to detect failed jobs and re-run them automatically.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Automatically detect and retry cron jobs that failed due to network/connection errors.
Add this to your HEARTBEAT.md: ## Cron Recovery Check Check for cron jobs with lastStatus: "error". If the error matches network patterns (connection error, sendMessage failed, fetch failed, ETIMEDOUT, ECONNREFUSED), retry the job using cron tool with action: "run" and the job ID. Report what was recovered. That's it. On each heartbeat, failed network jobs get retried automatically.
On heartbeat, check all cron jobs via cron list Filter for jobs where lastStatus = "error" and enabled = true Check if lastError matches network-related patterns Re-run eligible jobs via cron run Report results
These errors indicate transient network issues worth retrying: Network request.*failed Connection error ECONNREFUSED ETIMEDOUT ENOTFOUND sendMessage.*failed fetch failed socket hang up
Retried: Network timeouts Connection refused Message send failures DNS lookup failures Skipped (not retried): Logic errors (bad config, missing data) Auth failures Disabled jobs Jobs that just ran successfully
To check and retry failed jobs manually: # List all jobs and their status clawdbot cron list # Find failed jobs clawdbot cron list | jq '.jobs[] | select(.state.lastStatus == "error") | {name, error: .state.lastError}' # Retry a specific job clawdbot cron run --id <JOB_ID>
When implementing the heartbeat check: 1. Call cron tool with action: "list" 2. For each job in response.jobs: - Skip if job.enabled !== true - Skip if job.state.lastStatus !== "error" - Check if job.state.lastError matches network patterns - If retryable: call cron tool with action: "run", jobId: job.id 3. Report: "Recovered X jobs" or "No failed jobs to recover"
7:00 PM โ Evening briefing cron fires Network hiccup โ Telegram send fails Job marked lastStatus: "error", lastError: "Network request for 'sendMessage' failed!" 7:15 PM โ Connection restored, heartbeat runs Skill detects the failed job, sees it's a network error Retries the job โ briefing delivered Reports: "Recovered 1 job: evening-wrap-briefing"
Only retries transient network errors Respects job enabled state Won't create retry loops (checks lastRunAtMs) Reports all recovery attempts
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.