[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758JC8XGVTDFW736N5ZCQQD":3,"skill-same:01M758JC8XGVTDFW736N5ZCQQD":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M758JC8XGVTDFW736N5ZCQQD","telegram-delivery-diagnostics",null,"Diagnose and fix Telegram delivery issues for Hermes cron jobs — delivery pipeline tracing, DNS\u002Fnetwork diagnostics, adapter state verification, and known failure patterns.","lukemcqueen\u002Fsteadfaste-fleet","lukemcqueen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F405240?v=4","01M757MHPAGRXTJAT46SKZP98R","Luke McQueen","01M757MHPZ573KP8DT9GB8SBQ7",4,"MIT","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ftelegram-delivery-diagnostics\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: telegram-delivery-diagnostics\ndescription: Diagnose and fix Telegram delivery issues for Hermes cron jobs — delivery pipeline tracing, DNS\u002Fnetwork diagnostics, adapter state verification, and known failure patterns.\ncategory: devops\nauthor: Steadfaste Fleet\nversion: 1.0.0\nplatforms: [linux, macos]\n---\n\n# Telegram Delivery Diagnostics\n\nDiagnose why a Hermes cron job's output didn't reach the user on Telegram.\n\n## When to use\n\n- User says \"I didn't get my news\u002Fbrief\u002Falert today\"\n- Cron job logs `delivered` but user didn't see it\n- Gateway.log shows Telegram DNS failures or fallback IP flapping\n- After a network outage or DNS resolver change\n- When adding a new cron with Telegram delivery target\n\n## Architecture — How Cron Deliveries Work\n\n```\nCron job finishes\n  → scheduler.py queues delivery via gateway's event loop (future)\n  → DeliveryRouter._deliver_to_platform()\n  → Telegram adapter.send()\n     → self._bot.send_message() (python-telegram-bot)\n        → httpx client with TelegramFallbackTransport\n           → Primary DNS: api.telegram.org\n           → Fallback: 149.154.166.110, 149.154.167.220\n     → 3 retry attempts per chunk on NetworkError\n  → Returns SendResult(success=True, message_id=...)\n  → Scheduler logs: \"delivered to telegram:CHAT_ID via live adapter\"\n```\n\n### Two delivery paths\n\n| Path | When | Mechanism |\n|------|------|-----------|\n| **Live adapter** | Default for all crons | Goes through gateway's adapter (`adapter.send()`). Returns success\u002Ffailure. |\n| **Standalone** | Live adapter unavailable or timed out | Direct HTTP to Telegram API via `_send_to_platform()`. Bypasses gateway entirely. |\n\n### Key configuration points\n\n| Layer | What to check | File |\n|-------|--------------|------|\n| Bot token | `TELEGRAM_BOT_TOKEN` | `~\u002F.hermes\u002F.env` |\n| Home channel | `TELEGRAM_HOME_CHANNEL` (should match user chat_id) | `~\u002F.hermes\u002F.env` |\n| Allowed users | `TELEGRAM_ALLOWED_USERS` | `~\u002F.hermes\u002F.env` |\n| Platform config | `display.platforms.telegram.streaming: true` | `~\u002F.hermes\u002Fconfig.yaml` |\n| IPv4 preference | `network.force_ipv4: true` | `~\u002F.hermes\u002Fconfig.yaml` |\n| Fallback IPs | `TELEGRAM_FALLBACK_IPS` env var (optional, overrides defaults) | `~\u002F.hermes\u002F.env` or config |\n| Cron delivery target | Format: `telegram:CHAT_ID` | Cron job definition |\n\n## Verification checklist\n\nWhen a user reports missing delivery, run through these in order:\n\n### 1. Check cron ran successfully\n\n```bash\ncronjob action='list' --filter \u003Cjob-name>\n# Check: last_status == \"ok\", last_delivery_error == null\n```\n\n### 2. Check delivery log in agent.log\n\n```\ngrep \"\u003CJOB_ID>.*delivered\" ~\u002F.hermes\u002Flogs\u002Fagent.log\n# Should say \"delivered to telegram:\u003CTELEGRAM_HOME_CHANNEL> via live adapter\"\n```\n\n### 3. Check gateway delivery log\n\n```bash\ngrep -a \"\u003CJOB_ID>\" ~\u002F.hermes\u002Flogs\u002Fgateway.log\n# Should show \"Cron output preserved for chunking adapter\" if message > 4000 chars\n# NO error after this entry means send was successful\n```\n\n### 4. Check Telegram API connectivity\n\n```bash\n# Test directly (bypasses gateway)\nTOKEN=$(grep \"^TELEGRAM_BOT_TOKEN=\" ~\u002F.hermes\u002F.env | cut -d= -f2-)\ncurl -s --max-time 10 \"https:\u002F\u002Fapi.telegram.org\u002Fbot${TOKEN}\u002FgetMe\"\n# Expect: {\"ok\":true,\"result\":{\"id\":...,\"is_bot\":true,...}}\n\n# Test sendMessage\ncurl -s --max-time 10 -X POST \"https:\u002F\u002Fapi.telegram.org\u002Fbot${TOKEN}\u002FsendMessage\" \\\n  -d \"chat_id=${TELEGRAM_HOME_CHANNEL}\" -d \"text=🧪 Diagnostics test\"\n```\n\n### 5. Check DNS resolution\n\n```bash\n# System DNS\ngetent hosts api.telegram.org\n# Should return an IPv4 address (149.154.166.110)\n# If IPv6 (2001:67c:4e8:f004::9) appears, IPv6 may be failing\n\n# Check if force_ipv4 patch is active\npython3 -c \"\nimport socket\nprint('Patched:', getattr(socket.getaddrinfo, '_hermes_ipv4_patched', False))\n\"\n\n# Full DNS diagnostics\nfor i in 1 2 3 4 5; do\n  dig +short api.telegram.org @192.168.1.1 2>\u002Fdev\u002Fnull\ndone\n# If results are inconsistent → DNS flapping\n```\n\n### 6. Check gateway Telegram connection state\n\n```bash\ngrep -a \"Telegram\" ~\u002F.hermes\u002Flogs\u002Fgateway.log | grep \"07-08\" | tail -10\n# Look for: \n# - \"sticky fallback IP\" → DNS was failing, using fallback\n# - \"sticky fallback IP failed\" → fallback ALSO failed\n# - \"polling resumed\" → recovered\n# - \"polling reconnect failed\" → still down\n```\n\n## Known failure patterns\n\n### Pattern A: DNS flapping — systemd-resolved intermittent failures\n\n**Symptom:** `[Errno -2] Name or service not known` in errors.log, followed by automatic fallback IP usage. Cron deliveries may succeed or fail depending on timing.\n\n**Root cause:** System DNS resolver (192.168.1.1 via systemd-resolved) intermittently fails to resolve `api.telegram.org`. The TelegramFallbackTransport handles this by retrying fallback IPs `149.154.166.110`, `149.154.167.220`.\n\n**Impact:** \n- Send path has its OWN transport (separate from polling)\n- Each send gets 3 retries with fallback IPs\n- During periods when BOTH DNS and fallback IPs fail, sends fail\n- The `force_ipv4: true` config can't help when DNS itself is unreachable\n\n**Fix:**\n1. (Preferred) Pin IPv4 in `\u002Fetc\u002Fhosts`:\n   ```\n   echo \"149.154.166.110 api.telegram.org\" | sudo tee -a \u002Fetc\u002Fhosts\n   ```\n   This bypasses system DNS entirely for `api.telegram.org`.\n\n2. (Already set) Ensure `network.force_ipv4: true` in `~\u002F.hermes\u002Fconfig.yaml`.\n   This monkey-patches `socket.getaddrinfo` to prefer `AF_INET` (IPv4) before IPv6.\n\n3. (Belt-and-suspenders) Set `TELEGRAM_FALLBACK_IPS` in `.env` to ensure fallback is always configured.\n\n### Pattern B: IPv6 connectivity failures\n\n**Symptom:** `api.telegram.org` resolves to BOTH `149.154.166.110` (IPv4) and `2001:67c:4e8:f004::9` (IPv6). `ping6` to the IPv6 address fails, but Python's httpx may attempt IPv6 first and time out.\n\n**Diagnosis:**\n```bash\nping6 -c1 -W2 2001:67c:4e8:f004::9\n# If FAIL → IPv6 is broken on this network\nresolvectl query api.telegram.org\n# Shows both addresses\n```\n\n**Fix:** Same as Pattern A — `\u002Fetc\u002Fhosts` IPv4 pinning eliminates IPv6 resolution entirely.\n\n### Pattern C: Telegram-side delivery gap (API accepts but doesn't deliver)\n\n**Symptom:** All system logs show successful delivery (adapter.send() returned success, message_ids received), but user reports messages never arrived. This is rare but documented on Telegram's side.\n\n**Diagnosis:** Only diagnosable by exclusion — if all system-side checks pass and the user confirms a test message sent NOW arrives, the earlier messages were likely lost in a Telegram-side transient delivery gap.\n\n**Fix:** No server-side fix. If it happens, note the time and check Telegram status pages.\n\n### Pattern D: Adapter not initialized for cron delivery\n\n**Symptom:** `send_result` is None or \"Not connected\", cron falls through to standalone path.\n\n**Diagnosis:** Check gateway.log for Telegram adapter initialization errors:\n```bash\ngrep -a \"Not connected\\|send_path_degraded\\|adapter.*failed\" ~\u002F.hermes\u002Flogs\u002Fgateway.log\n```\n\n**Fix:** Restart the gateway: `hermes restart`.\n\n### Pattern E: Thread\u002Ftopic delivery goes to wrong lane\n\n**Symptom:** Private DM topic deliveries end up in the General topic instead of the named thread.\n\n**When it happens:** Cron deliveries with `attach_to_session: true` create named private DM topics. If the topic creation fails or the thread_id is wrong, messages fall through to the wrong lane.\n\n**Fix:** Check `thread_id` in the cron's origin metadata. For regular DM deliveries (no thread), ensure `deliver: telegram:CHAT_ID` has no thread_id component.\n\n## Log reference\n\n### Where to look\n\n| Log | Path | What it tells you |\n|-----|------|-------------------|\n| Cron scheduler | `~\u002F.hermes\u002Flogs\u002Fagent.log` | Job ran, delivered status, delivery errors |\n| Gateway delivery | `~\u002F.hermes\u002Flogs\u002Fgateway.log` | Output received, adapter.send() called, Telegram connectivity |\n| Errors | `~\u002F.hermes\u002Flogs\u002Ferrors.log` | DNS failures, Telegram network errors, adapter connection issues |\n\n### Key log patterns\n\n**Successful delivery (normal):**\n```\nINFO gateway.delivery: Cron output preserved for chunking adapter (8050 chars)\nINFO cron.scheduler: Job 'JOB_ID': delivered to telegram:\u003CTELEGRAM_HOME_CHANNEL> via live adapter\n```\n\n**Successful delivery (small message — under 4000 chars, no chunking):**\n```\nINFO cron.scheduler: Job 'JOB_ID': delivered to telegram:\u003CTELEGRAM_HOME_CHANNEL> via live adapter\n```\n(No \"Cron output preserved\" log — message was small enough to send directly.)\n\n**DNS failure with fallback recovery:**\n```\nWARNING plugins.platforms.telegram.telegram_network: Primary api.telegram.org connection failed\nWARNING plugins.platforms.telegram.telegram_network: ... path unreachable; using sticky fallback IP 149.154.166.110\n```\n\n**Total connectivity loss (both DNS and fallback fail):**\n```\nWARNING plugins.platforms.telegram.telegram_network: Primary api.telegram.org connection failed\nWARNING plugins.platforms.telegram.telegram_network: Fallback IP 149.154.166.110 failed\nWARNING plugins.platforms.telegram.telegram_network: Sticky fallback IP ... failed; resetting to primary DNS path\n```\n\n**Delivery timeout — assumed delivered (in flight):**\n```\nWARNING cron.scheduler: Job 'JOB_ID': live adapter send to telegram:CHAT_ID timed out after 60s; already dispatched, assuming delivered\n```\n\n**Delivery timeout — standalone fallback:**\n```\nWARNING cron.scheduler: Job 'JOB_ID': live adapter send ... timed out before the coroutine was dispatched, falling back to standalone\n```\n\n**Live adapter routine responses to user-initiated messages:**\n```\nINFO gateway.platforms.base: [Telegram] Sending response (N chars) to CHAT_ID\nINFO hermes_plugins.telegram_platform.adapter: [Telegram] Flushing text batch agent:main:telegram:dm:CHAT_ID (N chars)\n```\n\n## Pitfalls\n\n- **\"Delivered via live adapter\" ≠ proof the user saw it.** The log only proves Telegram's API returned a 200. Telegram can accept messages and fail to deliver them to the user's client.\n- **gateway.log is a binary file** (contains control characters). Always use `grep -a` when searching it.\n- **force_ipv4 doesn't fix all DNS issues.** The monkey-patch prefers IPv4 but can't help when the DNS server itself is unreachable (`[Errno -2]`). Use `\u002Fetc\u002Fhosts` pinning for that case.\n- **Cron deliveries use a different log path than interactive responses.** Interactive messages show `Sending response` in gateway.log. Cron deliveries go through `adapter.send()` directly and don't produce that log line. Don't assume a missing \"Sending response\" means failure.\n- **splits_long_messages = True means long crons are chunked.** The chunking adapter (`splits_long_messages=True`) means messages over 4000 chars are split. Each chunk gets its own `send_message` API call. If one chunk fails after all 3 retries, the ENTIRE send fails.\n- **Fallback IPs can also fail.** The seed fallback IPs (149.154.166.110, 149.154.167.220) are stable Telegram Bot API endpoints but can be unreachable from certain geographic regions during network events.\n- **Two transports, one adapter.** The Telegram adapter creates TWO `TelegramFallbackTransport` instances — one for requests (sending) and one for get_updates (polling). Each has its own primary transport, fallback transports, and sticky IP. The send path's transport is independent of the polling path's connectivity.\n","# Telegram Delivery Diagnostics\n\nDiagnose why a Hermes cron job's output didn't reach the user on Telegram.\n\n## When to use\n\n- User says \"I didn't get my news\u002Fbrief\u002Falert today\"\n- Cron job logs `delivered` but user didn't see it\n- Gateway.log shows Telegram DNS failures or fallback IP flapping\n- After a network outage or DNS resolver change\n- When adding a new cron with Telegram delivery target\n\n## Architecture — How Cron Deliveries Work\n\n```\nCron job finishes\n  → scheduler.py queues delivery via gateway's event loop (future)\n  → DeliveryRouter._deliver_to_platform()\n  → Telegram adapter.send()\n     → self._bot.send_message() (python-telegram-bot)\n        → httpx client with TelegramFallbackTransport\n           → Primary DNS: api.telegram.org\n           → Fallback: 149.154.166.110, 149.154.167.220\n     → 3 retry attempts per chunk on NetworkError\n  → Returns SendResult(success=True, message_id=...)\n  → Scheduler logs: \"delivered to telegram:CHAT_ID via live adapter\"\n```\n\n### Two delivery paths\n\n| Path | When | Mechanism |\n|------|------|-----------|\n| **Live adapter** | Default for all crons | Goes through gateway's adapter (`adapter.send()`). Returns success\u002Ffailure. |\n| **Standalone** | Live adapter unavailable or timed out | Direct HTTP to Telegram API via `_send_to_platform()`. Bypasses gateway entirely. |\n\n### Key configuration points\n\n| Layer | What to check | File |\n|-------|--------------|------|\n| Bot token | `TELEGRAM_BOT_TOKEN` | `~\u002F.hermes\u002F.env` |\n| Home channel | `TELEGRAM_HOME_CHANNEL` (should match user chat_id) | `~\u002F.hermes\u002F.env` |\n| Allowed users | `TELEGRAM_ALLOWED_USERS` | `~\u002F.hermes\u002F.env` |\n| Platform config | `display.platforms.telegram.streaming: true` | `~\u002F.hermes\u002Fconfig.yaml` |\n| IPv4 preference | `network.force_ipv4: true` | `~\u002F.hermes\u002Fconfig.yaml` |\n| Fallback IPs | `TELEGRAM_FALLBACK_IPS` env var (optional, overrides defaults) | `~\u002F.hermes\u002F.env` or config |\n| Cron delivery target | Format: `telegram:CHAT_ID` | Cron job definition |\n\n## Verification checklist\n\nWhen a user reports missing delivery, run through these in order:\n\n### 1. Check cron ran successfully\n\n```bash\ncronjob action='list' --filter \u003Cjob-name>\n# Check: last_status == \"ok\", last_delivery_error == null\n```\n\n### 2. Check delivery log in agent.log\n\n```\ngrep \"\u003CJOB_ID>.*delivered\" ~\u002F.hermes\u002Flogs\u002Fagent.log\n# Should say \"delivered to telegram:\u003CTELEGRAM_HOME_CHANNEL> via live adapter\"\n```\n\n### 3. Check gateway delivery log\n\n```bash\ngrep -a \"\u003CJOB_ID>\" ~\u002F.hermes\u002Flogs\u002Fgateway.log\n# Should show \"Cron output preserved for chunking adapter\" if message > 4000 chars\n# NO error after this entry means send was successful\n```\n\n### 4. Check Telegram API connectivity\n\n```bash\n# Test directly (bypasses gateway)\nTOKEN=$(grep \"^TELEGRAM_BOT_TOKEN=\" ~\u002F.hermes\u002F.env | cut -d= -f2-)\ncurl -s --max-time 10 \"https:\u002F\u002Fapi.telegram.org\u002Fbot${TOKEN}\u002FgetMe\"\n# Expect: {\"ok\":true,\"result\":{\"id\":...,\"is_bot\":true,...}}\n\n# Test sendMessage\ncurl -s --max-time 10 -X POST \"https:\u002F\u002Fapi.telegram.org\u002Fbot${TOKEN}\u002FsendMessage\" \\\n  -d \"chat_id=${TELEGRAM_HOME_CHANNEL}\" -d \"text=🧪 Diagnostics test\"\n```\n\n### 5. Check DNS resolution\n\n```bash\n# System DNS\ngetent hosts api.telegram.org\n# Should return an IPv4 address (149.154.166.110)\n# If IPv6 (2001:67c:4e8:f004::9) appears, IPv6 may be failing\n\n# Check if force_ipv4 patch is active\npython3 -c \"\nimport socket\nprint('Patched:', getattr(socket.getaddrinfo, '_hermes_ipv4_patched', False))\n\"\n\n# Full DNS diagnostics\nfor i in 1 2 3 4 5; do\n  dig +short api.telegram.org @192.168.1.1 2>\u002Fdev\u002Fnull\ndone\n# If results are inconsistent → DNS flapping\n```\n\n### 6. Check gateway Telegram connection state\n\n```bash\ngrep -a \"Telegram\" ~\u002F.hermes\u002Flogs\u002Fgateway.log | grep \"07-08\" | tail -10\n# Look for: \n# - \"sticky fallback IP\" → DNS was failing, using fallback\n# - \"sticky fallback IP failed\" → fallback ALSO failed\n# - \"polling resumed\" → recovered\n# - \"polling reconnect failed\" → still down\n```\n\n## Known failure patterns\n\n### Pattern A: DNS flapping — systemd-resolved intermittent failures\n\n**Symptom:** `[Errno -2] Name or service not known` in errors.log, followed by automatic fallback IP usage. Cron deliveries may succeed or fail depending on timing.\n\n**Root cause:** System DNS resolver (192.168.1.1 via systemd-resolved) intermittently fails to resolve `api.telegram.org`. The TelegramFallbackTransport handles this by retrying fallback IPs `149.154.166.110`, `149.154.167.220`.\n\n**Impact:** \n- Send path has its OWN transport (separate from polling)\n- Each send gets 3 retries with fallback IPs\n- During periods when BOTH DNS and fallback IPs fail, sends fail\n- The `force_ipv4: true` config can't help when DNS itself is unreachable\n\n**Fix:**\n1. (Preferred) Pin IPv4 in `\u002Fetc\u002Fhosts`:\n   ```\n   echo \"149.154.166.110 api.telegram.org\" | sudo tee -a \u002Fetc\u002Fhosts\n   ```\n   This bypasses system DNS entirely for `api.telegram.org`.\n\n2. (Already set) Ensure `network.force_ipv4: true` in `~\u002F.hermes\u002Fconfig.yaml`.\n   This monkey-patches `socket.getaddrinfo` to prefer `AF_INET` (IPv4) before IPv6.\n\n3. (Belt-and-suspenders) Set `TELEGRAM_FALLBACK_IPS` in `.env` to ensure fallback is always configured.\n\n### Pattern B: IPv6 connectivity failures\n\n**Symptom:** `api.telegram.org` resolves to BOTH `149.154.166.110` (IPv4) and `2001:67c:4e8:f004::9` (IPv6). `ping6` to the IPv6 address fails, but Python's httpx may attempt IPv6 first and time out.\n\n**Diagnosis:**\n```bash\nping6 -c1 -W2 2001:67c:4e8:f004::9\n# If FAIL → IPv6 is broken on this network\nresolvectl query api.telegram.org\n# Shows both addresses\n```\n\n**Fix:** Same as Pattern A — `\u002Fetc\u002Fhosts` IPv4 pinning eliminates IPv6 resolution entirely.\n\n### Pattern C: Telegram-side delivery gap (API accepts but doesn't deliver)\n\n**Symptom:** All system logs show successful delivery (adapter.send() returned success, message_ids received), but user reports messages never arrived. This is rare but documented on Telegram's side.\n\n**Diagnosis:** Only diagnosable by exclusion — if all system-side checks pass and the user confirms a test message sent NOW arrives, the earlier messages were likely lost in a Telegram-side transient delivery gap.\n\n**Fix:** No server-side fix. If it happens, note the time and check Telegram status pages.\n\n### Pattern D: Adapter not initialized for cron delivery\n\n**Symptom:** `send_result` is None or \"Not connected\", cron falls through to standalone path.\n\n**Diagnosis:** Check gateway.log for Telegram adapter initialization errors:\n```bash\ngrep -a \"Not connected\\|send_path_degraded\\|adapter.*failed\" ~\u002F.hermes\u002Flogs\u002Fgateway.log\n```\n\n**Fix:** Restart the gateway: `hermes restart`.\n\n### Pattern E: Thread\u002Ftopic delivery goes to wrong lane\n\n**Symptom:** Private DM topic deliveries end up in the General topic instead of the named thread.\n\n**When it happens:** Cron deliveries with `attach_to_session: true` create named private DM topics. If the topic creation fails or the thread_id is wrong, messages fall through to the wrong lane.\n\n**Fix:** Check `thread_id` in the cron's origin metadata. For regular DM deliveries (no thread), ensure `deliver: telegram:CHAT_ID` has no thread_id component.\n\n## Log reference\n\n### Where to look\n\n| Log | Path | What it tells you |\n|-----|------|-------------------|\n| Cron scheduler | `~\u002F.hermes\u002Flogs\u002Fagent.log` | Job ran, delivered status, delivery errors |\n| Gateway delivery | `~\u002F.hermes\u002Flogs\u002Fgateway.log` | Output received, adapter.send() called, Telegram connectivity |\n| Errors | `~\u002F.hermes\u002Flogs\u002Ferrors.log` | DNS failures, Telegram network errors, adapter connection issues |\n\n### Key log patterns\n\n**Successful delivery (normal):**\n```\nINFO gateway.delivery: Cron output preserved for chunking adapter (8050 chars)\nINFO cron.scheduler: Job 'JOB_ID': delivered to telegram:\u003CTELEGRAM_HOME_CHANNEL> via live adapter\n```\n\n**Successful delivery (small message — under 4000 chars, no chunking):**\n```\nINFO cron.scheduler: Job 'JOB_ID': delivered to telegram:\u003CTELEGRAM_HOME_CHANNEL> via live adapter\n```\n(No \"Cron output preserved\" log — message was small enough to send directly.)\n\n**DNS failure with fallback recovery:**\n```\nWARNING plugins.platforms.telegram.telegram_network: Primary api.telegram.org connection failed\nWARNING plugins.platforms.telegram.telegram_network: ... path unreachable; using sticky fallback IP 149.154.166.110\n```\n\n**Total connectivity loss (both DNS and fallback fail):**\n```\nWARNING plugins.platforms.telegram.telegram_network: Primary api.telegram.org connection failed\nWARNING plugins.platforms.telegram.telegram_network: Fallback IP 149.154.166.110 failed\nWARNING plugins.platforms.telegram.telegram_network: Sticky fallback IP ... failed; resetting to primary DNS path\n```\n\n**Delivery timeout — assumed delivered (in flight):**\n```\nWARNING cron.scheduler: Job 'JOB_ID': live adapter send to telegram:CHAT_ID timed out after 60s; already dispatched, assuming delivered\n```\n\n**Delivery timeout — standalone fallback:**\n```\nWARNING cron.scheduler: Job 'JOB_ID': live adapter send ... timed out before the coroutine was dispatched, falling back to standalone\n```\n\n**Live adapter routine responses to user-initiated messages:**\n```\nINFO gateway.platforms.base: [Telegram] Sending response (N chars) to CHAT_ID\nINFO hermes_plugins.telegram_platform.adapter: [Telegram] Flushing text batch agent:main:telegram:dm:CHAT_ID (N chars)\n```\n\n## Pitfalls\n\n- **\"Delivered via live adapter\" ≠ proof the user saw it.** The log only proves Telegram's API returned a 200. Telegram can accept messages and fail to deliver them to the user's client.\n- **gateway.log is a binary file** (contains control characters). Always use `grep -a` when searching it.\n- **force_ipv4 doesn't fix all DNS issues.** The monkey-patch prefers IPv4 but can't help when the DNS server itself is unreachable (`[Errno -2]`). Use `\u002Fetc\u002Fhosts` pinning for that case.\n- **Cron deliveries use a different log path than interactive responses.** Interactive messages show `Sending response` in gateway.log. Cron deliveries go through `adapter.send()` directly and don't produce that log line. Don't assume a missing \"Sending response\" means failure.\n- **splits_long_messages = True means long crons are chunked.** The chunking adapter (`splits_long_messages=True`) means messages over 4000 chars are split. Each chunk gets its own `send_message` API call. If one chunk fails after all 3 retries, the ENTIRE send fails.\n- **Fallback IPs can also fail.** The seed fallback IPs (149.154.166.110, 149.154.167.220) are stable Telegram Bot API endpoints but can be unreachable from certain geographic regions during network events.\n- **Two transports, one adapter.** The Telegram adapter creates TWO `TelegramFallbackTransport` instances — one for requests (sending) and one for get_updates (polling). Each has its own primary transport, fallback transports, and sticky IP. The send path's transport is independent of the polling path's connectivity.\n",{"name":5,"author":24,"version":25,"category":26,"platforms":27,"description":7},"Steadfaste Fleet","1.0.0","devops",[28,29],"linux","macos","main","2e6aa8d15ab0a366c90be54f61bf9c6e97015e83","skills\u002Fdevops\u002Ftelegram-delivery-diagnostics",1,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet","steadfaste.com","https:\u002F\u002Fgithub.com\u002Flukemcqueen","AI Architect | Building Hermes Cortex: governed multi-agent AI for autonomous software engineering | Enterprise Tech Consultant","2026-11-14 22:33:34",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add lukemcqueen\u002Fsteadfaste-fleet --skill telegram-delivery-diagnostics",{"tool":45,"command":46},"bunx","bunx skills add lukemcqueen\u002Fsteadfaste-fleet --skill telegram-delivery-diagnostics",{"tool":48,"command":49},"pnpm","pnpm dlx skills add lukemcqueen\u002Fsteadfaste-fleet --skill telegram-delivery-diagnostics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ftelegram-delivery-diagnostics\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fdelivery-pipeline-anatomy.md","REFERENCE","参考文档",6752,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ftelegram-delivery-diagnostics\u002Freferences\u002Fdelivery-pipeline-anatomy.md",[60,68,75,82,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M7DXY4G8NSVB59K8B6S2AQNP","macbook-linux-maintenance","Legacy MacBook Linux fixes: GPU wedge, reboot hang, thermal.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fmacbook-linux-maintenance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":67},"01M7DXXYJCXFJ3TGB84ZQ8KFE6","governance-regression-triage","Triage a host's governance issues: what changed.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fgovernance-regression-triage\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":67},"01M7DXXSAP1G8FDRJAMXQGBBMK","enforcement-immutability","Use when enforcement files lose their immutable flag.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fenforcement-immutability\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":67},"01M78SSDQVRYX64Y16X32TC0NS","steadfaste-fleet-repo-deploy","Use when committing to the steadfaste-fleet repo.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-repo-deploy\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":67},"01M78SS928F3R2RJAYVW4E30CE","steadfaste-fleet-maintenance","Maintain an installed Steadfaste Fleet instance — update both the upstream Hermes Agent and the fleet repo layer, merge diverged histories, sync skills safely, and troubleshoot common issues. Covers the dual-update workflow (hermes update + fleet-update.sh), encrypted brain data backup, mycortex import, and recovery techniques.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-maintenance\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":67},"01M78SP1CHW0T0BWE5ZT6JBPX8","fleet-preflight","DEPRECATED alias — merged into survey-before-action (2026-08-20). Load survey-before-action instead; its \"Repo-Specific Pre-Flight\" section covers git search, Hermes boundary, and deployment verification.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ffleet-preflight\u002FSKILL.md",[],[]]