cron-retry

Retry failed cron jobs after network recovery with recovery reporting.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/vuxsoul-ui/catclash --skill cron-retry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cron-retry
Source: https://github.com/vuxsoul-ui/catclash/tree/main/skills/cron-retry
Command: npx skills add https://github.com/vuxsoul-ui/catclash --skill cron-retry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Automatically detect and retry cron jobs that failed due to network/connection errors.
  • Respect job enabled state and only retry transient failures, with clear recovery reporting.

Quick Start

Configure the heartbeat to automatically retry failed cron jobs when connectivity is restored.

Frequently Asked Questions about cron-retry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically retry failed cron jobs after a network recovery?

You can automatically retry failed cron jobs after network recovery by integrating heartbeat detection to identify transient connectivity errors and re-running the affected jobs once connectivity is restored.

What mechanism triggers an automatic cron job retry for connection errors?

The mechanism triggers a retry by checking if the job's lastStatus is 'error' and the lastError matches network patterns, then automatically re-running the job when the heartbeat detects restored connectivity.

Can I configure cron job retries to only target transient network failures?

Yes, you can filter retries to only target transient network failures by checking that the job is enabled and its lastError specifically matches network or connection error patterns before attempting re-execution.

Do I need a heartbeat-driven environment to auto-retry cron jobs?

Yes, you need a heartbeat-driven environment because the automation relies on heartbeat integration to detect connectivity restoration and list jobs that failed due to network errors for automatic retry.

What's the best way to manage cron job recovery in heartbeat-driven environments?

Automating recovery with a tool that filters enabled jobs by their error state and lastError network patterns ensures only transient failures are retried, providing clear reporting of recovered jobs.