cron-retry

To automatically retry failed cron jobs after network errors, you need a recovery mechanism that detects transient failures and re-runs the jobs once connectivity is restored. This requires heartbeat monitoring to identify error states and trigger retries.

Triggering an automatic cron job retry requires the job to have enabled = true, lastStatus = "error", and a lastError matching network patterns. Once these conditions are met, the system re-runs the job upon detecting restored connectivity.

Heartbeat monitoring for cron job recovery works by continuously checking job status to detect when a cron job enters an error state. When connectivity returns, it automatically identifies eligible network-related errors and re-runs the affected jobs.

Yes, you can selectively retry only network-related cron job failures. The system filters retries by checking if the job is enabled, has a lastStatus of "error", and if the lastError matches specific network patterns before triggering the re-run.

You get observability reports for recovered cron jobs by using a recovery tool that reports the outcomes of automated retry attempts. Additionally, it provides manual recovery steps if the automatic network error retry does not succeed.