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

Description and use

Auditing own n8n template catalog found zero retry configuration across all 13 HTTP Request nodes. After applying retryOnFail: true, maxTries: 3, waitBetweenTries: 5000, full QA gate passed 8/8 and three deliverable ZIPs were rebuilt.

Problem

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

Outcome

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.

Workflow

• 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

Evidence

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

Source

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

Source

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

Source

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

Source

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

Source