wiki: nightly audit 2026-10-01 — cron fleet re-verified, Telegram delivery root cause, memory hygiene

This commit is contained in:
Tony0410
2026-10-01 00:10:55 +08:00
parent 4e7d99064e
commit a32475bd54
8 changed files with 115 additions and 48 deletions
+10 -4
View File
@@ -3,11 +3,11 @@ title: Messaging Integrations
type: system
status: active
created: 2026-07-22
updated: 2026-07-22
verified_on: 2026-07-22
updated: 2026-10-01
verified_on: 2026-10-01
confidence: high
tags: [messaging, telegram, discord, email, integrations]
sources: [raw/configs/hermes-config-sanitized.txt]
sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json]
---
# Messaging Integrations
@@ -20,6 +20,11 @@ sources: [raw/configs/hermes-config-sanitized.txt]
- **Delivery targets seen in cron:** telegram, `telegram:1793951355`, `telegram:-1004321904721`, `telegram:-1004321904721:notifications`, `telegram:-1004321904721:102`, `telegram:-1004321904721:273`, `telegram:-1004321904721:346`, `telegram:-1004321904721:1030`
- **Notes:** Primary delivery target for scheduled jobs
### Delivery target semantics (verified 2026-10-01)
- A **bare `deliver: "telegram"` resolves to the home DM (`1793951355`)** — *not* to the primary group. It is not a "send to the main chat" shorthand.
- To reach a forum topic you must use the full form **`telegram:<chat_id>:<thread_id>`**, e.g. `telegram:-1004321904721:102`.
- Consequence: a job that names a group topic ID but is actually pointed at the DM hard-fails with `configured thread_id <n> … was not found` / `Message thread not found`, and **the message is lost** — it is not silently downgraded to a thread-less send. This caused the 2026-09-30 delivery incident on `fad5a86979d4`, `1b23c042e17d` and `c8d52904e1d6`.
## Discord
- **Status:** enabled, streaming true
- **Platform:** `hermes-discord`
@@ -45,7 +50,8 @@ sources: [raw/configs/hermes-config-sanitized.txt]
- **Home Assistant:** homeassistant-platform enabled
## Known Issues
- **Telegram thread delivery failures on `telegram:1793951355` (2026-09-30):** jobs `fad5a86979d4` and `1b23c042e17d` report `configured thread_id 34795 … was not found`, and `c8d52904e1d6` reports `Message thread not found` (`last_status: delivery_failed`). Content generation succeeds — only the thread target is wrong. Fix: recreate the topic, or clear `thread_id` on those jobs. See [[systems/scheduled-tasks]].
- **Telegram thread-delivery failures — resolved 2026-09-30.** Jobs `fad5a86979d4` and `1b23c042e17d` reported `configured thread_id 34795 … was not found`, and `c8d52904e1d6` reported `Message thread not found` (`last_status: delivery_failed`). Root cause was the *target*, not the topic: those jobs used a bare `deliver: "telegram"`, which resolves to the home DM where group topic IDs do not exist. `1b23c042e17d` and `c8d52904e1d6` were retargeted to `telegram:-1004321904721:102` and verified end-to-end. See [[systems/scheduled-tasks]].
- **Three jobs still deliver to the home DM via a bare `telegram` target** (`0e753e9720fd`, `fad5a86979d4`, `066bb5191280`). Not failing today, but they carry stale `thread_id` errors and sit in the same failure class as the incident above — retarget them to a group topic.
## Multi-bot group chat (open question, raised 2026-09-30)
Anthony asked whether his other Hermes instances (the estate VMs/CTs) could share a group chat.