📈 Cron Job Optimization Analysis — Hermes
Reviewed: June 4, 2026
Analysis Date: June 2026 | Scope: All cron jobs on the Hermes agent system | Jobs analyzed: 50+
Executive Summary
Hermes runs 50+ cron jobs spanning security, monitoring, content, and maintenance. Analysis reveals several optimization opportunities including timing consolidation, redundant overlap detection, and reliability improvements.
Current Schedule Map (Hourly View)
| Hour (UTC) | Jobs | Type |
|---|---|---|
| 00:00 | heartbeat (every 30 min), uptime-monitor (every 5 min) | Monitoring |
| 00:30 | stale-state-cleanup | Maintenance |
| 01:00 | log-rotation | Maintenance |
| 02:00 | masterdash-backup, (monthly) skill-freshness | Backup/Maint |
| 02:15 | datagate-db-backup | Backup |
| 03:00 | cron-recovery | Recovery |
| 04:00 | secrets-rotation (daily), content-audit (weekly) | Security |
| 04:15 | backup-verify (weekly) | Backup |
| 05:00 | vuln-scanner (weekly), pentest-scanner (weekly) | Security |
| 05:30 | task-priority-scorer | Agent |
| 06:00 | weekly-reports (Mon), Cve-monitor, weekly-content-scan (Mon) | Mixed |
| 06:15 | blocker-detector | Agent |
| 06:30 | dep-vuln-scanner | Security |
| 06:40 | daily-health-check | Health |
| 07:00 | log-analyzer, ssl-expiry-monitor, resource-monitor (6h) | Monitoring |
| 07:10-07:30 | morning-briefing, trending-scanner, keyword-finder | Agent |
| 08:00-08:30 | spam-scanner, threat-digest, incident-checklist, content-briefs | Mixed |
| 09:00 | security-review (weekly Mon) | Security |
| 10:00 | wp-update-tracker (Mon) | Maintenance |
| 11:00 | weekly-seo-digest (Mon) | Content |
| 12:00 | newsletter-cron (Mon) | Content |
| 14:00, 18:00 | spam-scanner | Maintenance |
| 23:55 | daily-cost-summary | Monitoring |
Optimization Findings
Identified Issues
| Monday Morning Cluster | 6 jobs between 05:00-12:00 UTC on Mondays. Some already staggered (good). Consider moving weekly-content-scan to Tuesday. |
| Duplicate Security Scans | vuln-scanner, pentest-scanner, dep-vuln-scanner, secrets-rotation all run Daily/Weekly. Consider consolidating into a single comprehensive security pipeline. |
| Content Brief Generator | Runs daily at 08:30 but content creation is currently gated (backlog >5). This script wastes resources producing briefs that won't be consumed. |
| Trending Topic Scanner | Runs daily at 07:20. Useful for identifying content opportunities but output goes nowhere while content gate is active. |
| Newsletter Cron | Runs Monday at 12:00 but SMTP is not yet configured (blocked). Script will silently fail until nl-3 is unblocked. |
Recommended Optimizations
| Recommendation | Impact | Effort |
|---|---|---|
| Move weekly-content-scan from Mon 06:00 to Tue 06:00 | Reduces Monday cluster | Low (1 line change) |
| Disable content-brief-generator while content gate is active | Saves ~2 min/day CPU | Low (comment out) |
| Consolidate 4 security scanners into single pipeline | Reduces redundant API calls | Medium (script rewrite) |
| Add error notification for newsletter-cron (currently silent fail) | Prevents silent failures | Low (add stderr redirect) |
| Increase uptime-monitor interval from 5min to 15min (sufficient for shared hosting) | Reduces log noise 3x | Low (cron line change) |
Reliability Score
Current cron infrastructure scores 8.5/10 for reliability:
- ✔ Good: Staggered timing prevents most resource contention
- ✔ Good: Backup jobs properly separated from other operations
- ✔ Good: Cron-recovery system provides self-healing capability
- ⚠ Warning: 2 potentially wasted daily jobs (content-brief, trending-scanner) while content is gated
- ⚠ Warning: Newsletter cron will fail silently until SMTP is configured
- ⚠ Warning: Monday still has 6 jobs in ~7 hour window (mitigated by staggering)
Analysis performed by Hermes using crontab inspection. Recommendations are advisory. Low-effort changes can be applied autonomously; medium-effort changes require planning.