wiki audit 2026-10-02: 2 new cron failures, cliprox/terra connection auth incident, delivery-failure semantics corrected, profile rewrite, broken wikilinks repaired
- new: incidents/2026-10-01-cliproxy-connection-auth-expired.md (HTTP 401, credential fault, cannot self-recover)
- systems/scheduled-tasks.md: 30 jobs / 27 enabled; failing 3 -> 6; streaks advanced; wiki-tree drift recorded
- systems/messaging-integrations.md: two distinct thread-failure variants (lost vs thread-less fallback)
- systems/current-profile.md: full rewrite from live config (no profiles/default/, smart-route, OmniRoute)
- current-state.md / index.md / log.md: 2026-10-02 entry
- repair: copied 5 vault-only pages referenced by index.md (ignis, nextcloud, 3 incidents) so wikilinks resolve
- include pending stocktake output: skills-index.md 2026-09-27, raw/stocktake/freshness-2026-09-2{6,7}.txt
This commit is contained in:
@@ -3,8 +3,8 @@ title: Messaging Integrations
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-01
|
||||
verified_on: 2026-10-01
|
||||
updated: 2026-10-02
|
||||
verified_on: 2026-10-02
|
||||
confidence: high
|
||||
tags: [messaging, telegram, discord, email, integrations]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json]
|
||||
@@ -23,7 +23,10 @@ sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json]
|
||||
### 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`.
|
||||
- Consequence: a job that names a group topic ID but is actually pointed at the DM fails with `configured thread_id <n> … was not found` / `Message thread not found`. **Two variants are observed, and they behave differently** (verified 2026-10-02 against `~/.hermes/cron/executions.db`):
|
||||
- `Message thread not found` — hard failure, **the message is lost** (the 2026-09-30 incident variant).
|
||||
- `configured thread_id <n> for telegram:<dm> was not found; delivered without thread_id` — a **thread-less fallback send** does occur, yet the run is still recorded as `last_status: delivery_failed` / `delivery_outcome: failed`. Content reaches the DM; the delivery is marked failed anyway, so the job record reads like a lost message.
|
||||
- Do not assume "delivery failed" means the message never arrived — check the error variant before reporting a report as missing.
|
||||
|
||||
## Discord
|
||||
- **Status:** enabled, streaming true
|
||||
@@ -51,7 +54,7 @@ sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json]
|
||||
|
||||
## Known Issues
|
||||
- **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.
|
||||
- **Three jobs still deliver to the home DM via a bare `telegram` target** (`0e753e9720fd`, `fad5a86979d4`, `066bb5191280`). **No longer theoretical — two of them failed delivery on 2026-10-01:** `066bb5191280` (02:11) and `0e753e9720fd` (09:01) both recorded `delivery_outcome: failed` with the thread-less-fallback variant above, in the same failure class as the 2026-09-30 incident. Retarget them to `telegram:-1004321904721:<topic>`. See [[systems/scheduled-tasks]].
|
||||
|
||||
## 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.
|
||||
|
||||
Reference in New Issue
Block a user