Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Cron Internals

The cron subsystem provides scheduled task execution — from simple one shot delays to recurring cron expression jobs with skill injection and cross platform del

Developer Guide
Section
Developer Guide
Source
hermesbible.com/docs/developer-guide/cron-internals

The cron subsystem provides scheduled task execution — from simple one shot delays to recurring cron expression jobs with skill injection and cross platform del

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. Key Files
  2. Scheduling Model
  3. Job Storage
  4. Job Lifecycle States
  5. Backward Compatibility
  6. Scheduler Runtime
  7. Tick Cycle
  8. Gateway Integration
  9. Fresh Session Isolation
  10. Skill-Backed Jobs
  11. Script-Backed Jobs
  12. Provider Recovery
  13. Delivery Model
  14. Response Wrapping

Section map

Key Files

Maps key files to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Scheduling Model

Maps scheduling model to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Job Storage

Maps job storage to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Job Lifecycle States

Maps job lifecycle states to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Backward Compatibility

Maps backward compatibility to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Scheduler Runtime

Maps scheduler runtime to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Tick Cycle

Maps tick cycle to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Gateway Integration

Maps gateway integration to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Developer Guide 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: Key Files, Scheduling Model, Job Storage, Job Lifecycle States, Backward Compatibility. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: internals, subsystem, provides, scheduled, execution. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitDeveloper Guide documentation

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

Verify firstKey Files

Open the source anchor for Key Files 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 Developer Guide, then open the linked source page for exact current syntax.
  2. Start with the source section for Key Files; 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 Scheduling Model 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

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.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

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