Cron Troubleshooting
Cron حل المشكلات
Start with meaning, then move to detail.
This lesson explains Cron Troubleshooting as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Jobs Not Firing, Check 1: Verify the job exists and is active, Check 2: Confirm the schedule is correct, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Cron Troubleshooting without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Gateway
- The process that connects Hermes to channels such as Telegram or Discord and routes messages.
- Automation
- Running work later or repeatedly with explicit success and failure conditions.
Diagnose and fix common Hermes cron issues — jobs not firing, delivery failures, skill loading errors, and performance problems
What does the source say, and in what order?
- 01Jobs Not Firing
Start here to understand the core idea or structure.
- 02Check 1: Verify the job exists and is active
Read this after the foundation, then connect it to the previous step.
- 03Check 2: Confirm the schedule is correct
Read this after the foundation, then connect it to the previous step.
- 04Check 3: Is the gateway running?
Read this after the foundation, then connect it to the previous step.
- 05Check 4: Check the system clock and timezone
Read this after the foundation, then connect it to the previous step.
- 06Delivery Failures
Read this after the foundation, then connect it to the previous step.
- 07Check 1: Verify the deliver target is correct
Read this after the foundation, then connect it to the previous step.
- 08Check 2: Check [SILENT] usage
Read this after the foundation, then connect it to the previous step.
- 09Check 3: Platform token permissions
Read this after the foundation, then connect it to the previous step.
- 10Check 4: Response wrapping
Finish here to verify the result and special cases.
Copy only after you understand the effect.
hermes cron listdate
hermes cron list # Compare next_run times with local timecron:
wrap_response: falseRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.