skills.rest
huidge
huidgeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cron-job-troubleshooting

Diagnose cron job failures by analyzing status, logs, and gateway errors.

2|2|Updated Apr 16, 2026
Search Tags:#automation#troubleshooting#logs#diagnostics#cron#gateway#hermes
One-click install
npx skills add https://github.com/huidge/hermes-skills --skill cron-job-troubleshooting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cron-job-troubleshooting
Source: https://github.com/huidge/hermes-skills/tree/main/devops/cron-job-troubleshooting
Command: npx skills add https://github.com/huidge/hermes-skills --skill cron-job-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cron jobs often fail silently or run late, leading to missed tasks and degraded automation reliability. This skill helps identify the root causes and provides actionable steps to restore normal operation.

Core Features & Use Cases

  • Check job status via Hermes CLI or programmatic bindings to verify last_run_at, last_status, and next_run_at.
  • Inspect session files and system logs to diagnose delivery or processing errors.
  • Compare gateway code version with running process and perform safe restarts to reload updated providers.
  • Validate model availability and perform manual trigger tests to confirm end-to-end functionality.
  • Implement proactive monitoring and guardrails to detect and alert on recurring failures.

Quick Start

List cron jobs, review last_run_at and last_status, then trigger a manual run for the target job.

Frequently Asked Questions about cron-job-troubleshooting

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

FAQPage Schema
How do I troubleshoot cron job failures when tasks run late or silently fail?▼

To troubleshoot cron job failures, check the last_run_at, last_status, and next_run_at values via Hermes CLI or programmatic bindings to identify missed triggers and execution errors.

How do I check if a missed cron trigger was caused by a gateway outage?▼

Check gateway logs for error patterns and compare the current gateway code version with the running process to determine if an outage or stale code caused the missed cron trigger.

How do I diagnose delivery issues in Hermes cron jobs across different environments?▼

Diagnose Hermes delivery issues by inspecting session files and system logs to trace processing errors, then validate model availability to ensure end-to-end functionality across environments.

Do I need to restart the gateway after updating providers to fix cron execution errors?▼

Yes, you need to perform a safe gateway restart to reload updated providers and resolve execution errors caused by running outdated code versions in your cron environment.

What is the best way to proactively monitor cron jobs for recurring failures?▼

The best way to monitor recurring cron failures is to implement proactive guardrails that detect abnormal last_status changes and alert on recurring delivery or gateway processing issues.

Can I manually trigger a cron job to test if the end-to-end execution is working?▼

Yes, you can trigger a manual run for the target cron job to validate model availability, test end-to-end functionality, and confirm that the execution path is working normally.

Related Skills

Explore More Software Engineering Skills→
ldzhhxxldzhhxx
1

teams-meeting-pipeline

Automates Microsoft Teams meeting creation, management, and summarization via the Hermes CLI.

Community
Advanced
blocknaviblocknavi
1

convex-cron-jobs

Schedule recurring Convex functions with interval and cron expressions.

Official
Intermediate
ruchernchongruchernchong
12

crontab-manager

Manage cron jobs in crontab files with absolute paths and logging.

Community
Basic
zinohomezinohome

cron-jobs-writer

Validate and update OpenClaw cron job configurations in jobs.json files.

Community
Advanced