I Ran the 'Broken Template' Checklist on My Own n8n Workflows — Here's What I Found

说明与用途

对作者自己的 n8n 工作流目录进行了审计，发现所有 13 个 HTTP 请求节点均无重试配置。在已将每个节点的 retryOnFail 设置为 true、maxTries 设置为 3、waitBetweenTries 设置为 5000 后，完整 QA 门通过率为 8/8，三个交付 ZIP 包已从修复后的 JSON 重新构建。

问题

HTTP Request nodes in n8n workflow templates lack retry configuration, causing runs to silently fail on the first transient API failure.

结果

Zero retry configuration was found across all 13 HTTP Request nodes in the author's own catalog. After applying retryOnFail: true, maxTries: 3, waitBetweenTries: 5000 to each node, the full QA gate passed 8/8, and the three affected deliverable ZIPs were rebuilt.

工作流

• Grep the author's own catalog of 8 product files for HTTP Request nodes
• Apply retry configuration to each of the 13 HTTP Request nodes: retryOnFail: true, maxTries: 3, waitBetweenTries: 5000
• Re-run full QA gate on all 8 files: structural lint, real n8n import:workflow on a local instance, syntax checks on every Code node
• Rebuild the three affected deliverable ZIPs (Workflow Pack, Outbound Engine, free Starter Pack) from the fixed JSONs

证据

Result: zero retry configuration on all 13 nodes. Every single one would die silently on the first transient API failure.

来源

Each of the 13 nodes now has: retryOnFail: true, maxTries: 3, waitBetweenTries: 5000 (5 seconds between attempts)

来源

8/8 PASS. The three affected deliverable ZIPs (Workflow Pack, Outbound Engine, free Starter Pack) were rebuilt from the fixed JSONs.

来源

every HTTP request node in these workflows retries automatically (3 attempts, 5s apart) — one API hiccup won't silently kill your run.

来源

my n8n.io templates (5 approved, 1 under review) were deliberately left untouched — changing them means re-entering the official review queue

来源