Official issues about scheduled and recurring tasks. Sourced from the official GitHub repo; status derived from official labels; every entry links back to its source with a last-checked date.
Umbrella feature request describing multiple subsystems (cron, dashboard, desktop) that don't properly support non-default Hermes profiles, since the codebase assumes ~/.hermes/ is the canonical root instead of consistently resolving ~/.hermes/profiles/<name>/.
Duplicate report of the Telegram cron-job typing indicator persisting for the full subprocess lifetime instead of stopping at message delivery; closed as a duplicate.
A cron job's Telegram delivery keeps the typing indicator active for the entire lifetime of the job's subprocess rather than stopping once the delivery message is sent, which can last 30-60+ minutes for long-running jobs.
## 现象 在 Yuanbao 平台创建 cronjob 时用 `deliver=origin`，投递时好时坏。看日志基本就是两种结果： 1. 正常投递（live adapter 路径命中） 2.
Requests live status indicators (spinners, watch mode, heartbeat display) for kanban tasks in the TUI/CLI, since current output is static and requires manual re-running to see progress.
The cron scheduler sets HERMES_CRON_SESSION as a process-global environment variable, so once any cron job runs, all subsequent interactive gateway sessions in the same process are misclassified as cron sessions by the approval layer, permanently blocking execute_code under the default deny policy.
On Windows, creating a script-based no-agent cron job via hermes cron create --no-agent --script fails immediately with a 'str' object has no attribute 'exists' error before schedule validation runs.
On the macOS desktop app, a non-default profile shows sessions, channels, and cron jobs belonging to the default profile: a cross-profile data leak in the UI.
Since a prior fix (#22773), proactive cron deliveries to a Telegram threaded-DM forum topic land in the General topic instead due to a misclassification in cron/scheduler.py's DM-topic heuristic.
Cron deliveries targeting a Telegram private DM topic can fail to stay in that topic because the cron path only carries a generic thread_id, missing the metadata the adapter needs for private DM topics.
Cron jobs using OAuth-based providers fail with HTTP 429 when the credential pool is exhausted instead of falling back through the configured fallback_providers chain, unlike the main gateway/CLI session.
The Kanban board is currently separate from the Desktop app, requiring users to run CLI commands and manually copy task IDs; the issue proposes integrating it via a sidebar or in-chat /kanban commands.
In cron jobs, the memory tool is exposed to the agent but fails at runtime with 'Memory is not available', because cron sessions run with skip_memory=True while still inheriting the memory tool in their default toolset.
This RFC tracks the implemented Kanban board PR (#16100): a long-lived daemon replacing the cron-driven dispatcher, a drag-and-drop dashboard plugin, run history and worker log panels, live WebSocket updates, and multiple audit/review passes with concurrency and fuzz testing. Issue is closed as fixed, with further discussion moved to the PR.
Hermes cron job results delivered to the origin channel are visible only to the human and not mirrored into the live gateway session's context, so the main agent has no memory of completed scheduled tasks unless a human manually points it to a filesystem handoff file.
Back to curated issues . School solution cards . Troubleshooting