Hermes BibleUnofficial Docs
← All docs Docs / Guides & Tutorials

Cron Troubleshooting

When a cron job isn't behaving as expected, work through these checks in order. Most issues fall into one of four categories: timing, delivery, permissions, or

Guides & Tutorials
Section
Guides & Tutorials
Source
hermesbible.com/docs/guides/cron-troubleshooting

When a cron job isn't behaving as expected, work through these checks in order. Most issues fall into one of four categories: timing, delivery, permissions, or

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Jobs Not Firing
  2. Check 1: Verify the job exists and is active
  3. Check 2: Confirm the schedule is correct
  4. Check 3: Is the gateway running?
  5. Check 4: Check the system clock and timezone
  6. Delivery Failures
  7. Check 1: Verify the deliver target is correct
  8. Check 2: Check [SILENT] usage
  9. Check 3: Platform token permissions
  10. Check 4: Response wrapping
  11. Skill Loading Failures
  12. Check 1: Verify skills are installed
  13. Check 2: Check skill name vs. skill folder name
  14. Check 3: Skills that require interactive tools

Section map

Jobs Not Firing

Maps jobs not firing to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Check 1: Verify the job exists and is active

Maps check 1: verify the job exists and is active to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Check 2: Confirm the schedule is correct

Maps check 2: confirm the schedule is correct to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Check 3: Is the gateway running?

Maps check 3: is the gateway running? to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Check 4: Check the system clock and timezone

Maps check 4: check the system clock and timezone to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Delivery Failures

Maps delivery failures to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Check 1: Verify the deliver target is correct

Maps check 1: verify the deliver target is correct to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Check 2: Check [SILENT] usage

Maps check 2: check [silent] usage to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Guides & Tutorials doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Jobs Not Firing, Check 1: Verify the job exists and is active, Check 2: Confirm the schedule is correct, Check 3: Is the gateway running?, Check 4: Check the system clock and timezone. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: troubleshooting, behaving, expected, through, these. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitGuides & Tutorials documentation

Use when you need orientation for cron troubleshooting before applying exact upstream commands.

Verify firstJobs Not Firing

Open the source anchor for Jobs Not Firing and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Guides & Tutorials, then open the linked source page for exact current syntax.
  2. Start with the source section for Jobs Not Firing; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Check 1: Verify the job exists and is active if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page