Bug: cronjob run command fails to trigger execution (leaves job stuck in state: scheduled)

Environment

• Hermes Agent Version: latest/main
• Python: 3.13.11 (Miniconda3)
• System Python: 3.9.6
• croniter version: 6.2.2
• Platform: MacOS

Describe the bug

I attempted to manually trigger a newly created cron job using the cronjob run command. Although the API returns success: true, the job's last_run_at and last_status fields remain null. The job is stuck in state: scheduled and is never actually executed.

This also happens when using schedule: "every 1m" to force quick execution—it simply never triggers.

Steps To Reproduce

1. Create a cron job via API (e.g., cronjob create).
   • Prompt: "test news briefing..."
   • Schedule: every 240m
   • Response shows "state": "scheduled", "next_run_at": "2026-04-28T02:53..."
2. Execute cronjob run --job_id [job_id].
3. Observe the state.

Expected behavior

The command should either:

• Transition last_run_at to the current timestamp.
• Transition last_status to ok (or show a specific error).
• At least transition state to running immediately.

Actual behavior

The API command returns success: true, but inspecting the job state immediately after shows no changes. The job sits idle forever in state: scheduled with last_run_at: null.

API Response Snippets

cronjob create response:

{
  "success": true,
  "job": {
    "job_id": "cb7bb97c08c2",
    "state": "scheduled",
    "next_run_at": "2026-04-28T02:53:48...",
    "last_run_at": null,
    "last_status": null
  }
}

cronjob run response (after manual trigger):

{
  "success": true,
  "job": {
    "job_id": "cb7bb97c08c2",
    "state": "scheduled",
    "next_run_at": "2026-04-27T22:54:32...",
    "last_run_at": null,
    "last_status": null
  }
}

Pre-investigation (Environment)

• Verified Python environment is healthy.
• Verified croniter is correctly installed (v6.2.2) and functioning.
• python -c "import croniter; print('OK')" runs without error.
• The bug seems isolated to the scheduler triggering mechanism.

Additional Info

If there is a Discord or WeChat channel for reporting Hermes bugs, please point me there. This might be a blocking issue for the cron scheduling feature.