will/swarm-master
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record n8n IMAP reconnect mitigation

Browse Source
This commit is contained in:
William Valentin
2026-05-27 14:13:04 -07:00
parent da24b029b3
commit a5c105129e
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
swarm-common/obsidian-vault/will/will-shared-zap/Infrastructure/Automation/n8n IMAP Triage Pipeline.md
+9 -8
View File
@@ -3,7 +3,7 @@ title: n8n IMAP Triage Pipeline
area: infrastructure
tags: [n8n, imap, llm, automation, email]
created: 2026-03-27
updated: 2026-03-27
updated: 2026-05-27
status: active
related: [[Infrastructure/Automation/n8n Workflows]], [[Infrastructure/Architecture]]
---
@@ -31,8 +31,8 @@ Read Unseen Emails
## Local LLM
- **Model:** `gemma-3-12b-it-q4_0.gguf`
- **Endpoint:** `http://192.168.153.113:18806/v1/chat/completions`
- **Model:** `gemma-4-26B-A4B-it-UD-IQ2_M.gguf`
- **Endpoint:** `http://127.0.0.1:18806/v1/chat/completions` or LAN `http://192.168.153.130:18806/v1/chat/completions`
- **Used for:** ambiguous emails only
- **Reply shape:** JSON like `{"signal": true|false, "priority": 1|2|3, "reason": "..."}`
- **Priority scale:**
@@ -59,22 +59,23 @@ Sent to the local LLM for judgement.
### Obsidian
- writes per-email notes to `Notes/YYYY-MM-DD Subject.md`
- uses the Obsidian Local REST API at `http://192.168.153.113:27123`
- uses the Obsidian Local REST API at `http://127.0.0.1:27123` or LAN `http://192.168.153.130:27123`
## Important operational notes
- The Obsidian Local REST API must be reachable when the workflow runs.
- A major 2026-03-27 failure mode was **not** the LLM or the workflow logic — it was shared-vault cross-user permissions on the `virtiofs` mount. The API was up, but writes to some folders hung until permissions were fixed.
- On 2026-05-27, intermittent Gandi IMAP long-lived connection resets (`ECONNRESET`) were mitigated by setting the `Read Unseen Emails` node option `forceReconnect` to `10` minutes and restarting `n8n-agent`. Because n8n 2.x uses published workflow versions, the current workflow version was also inserted into `workflow_history` and the active/published version pointers were aligned. Backups were written under `~/.hermes/backups/n8n-imap-*`.
- First checks if this breaks again:
1. Obsidian Local REST API reachable?
2. shared vault path writable from host Obsidian user (`claw`) and VM assistant user (`openclaw`)?
3. local LLM endpoint still serving `gemma-3-12b-it-q4_0.gguf`?
2. shared vault path writable from the current host user / Obsidian Local REST process? Older `claw`/`openclaw` VM ownership issues are historical.
3. local LLM endpoint still serving `gemma-4-26B-A4B-it-UD-IQ2_M.gguf`?
4. IMAP trigger node still has `options.forceReconnect: 10`?
## Validation summary
Validated live on 2026-03-27:
- n8n healthy
- local Gemma endpoint healthy
- local Gemma endpoint healthy (current model re-checked 2026-05-27 as Gemma 4 26B GGUF)
- live local inference succeeded
- Telegram notifications previously verified
- Obsidian REST writes repaired and re-verified after permission fix