Five n8n Failure Drills Before Your Workflow Goes Live

说明与用途

n8n 的五个失败演练：从 401 到 429、400、重复事件和错误工作流。它们确保工作流程正确响应 API 错误并发送可靠警报。

问题

n8n workflows that call external APIs often fail with non‑200 responses; without pre‑live failure testing, minor glitches can become production incidents.

结果

The drills provide concrete evidence for each failure scenario, enabling operators to build robust error handling and reduce production incidents.

工作流

• 1. Configure a mock HTTP endpoint to return 401 Unauthorized and verify the workflow stops downstream writes, redacts tokens, and logs a redacted error.
• 2. Mock repeated 429 Too Many Requests with Retry‑After headers, confirm bounded exponential backoff with jitter, and ensure recovery or explicit failure.
• 3. Trigger a 400 Bad Request with malformed JSON, check that the workflow does not retry the same payload, and captures diagnostic details.
• 4. Replay a webhook event with a stable event_id to test idempotency; verify external side effects occur only once and that retries do not duplicate writes.
• 5. Force an error before an execution is saved to test the Error Trigger, ensuring execution.id/url are handled correctly and alerts are delivered reliably.

证据

Configure a mock HTTP endpoint to return 401 Unauthorized rather than a success payload. A safe workflow should stop the business action, identify the failing credential or endpoint, and report the failure without logging tokens or sensitive headers.

来源

Mock repeated 429 Too Many Requests responses, including a Retry-After header when provided. Check whether retries are bounded, whether they respect the provider's quota, and whether pending tasks are recoverable.

来源

A malformed JSON body or invalid required parameter can trigger 400 Bad Request. Retrying the same unchanged invalid payload repeatedly is not recovery.

来源

Send a repeated webhook event or re-run an interrupted execution using a stable test event_id. Verify whether the CRM record, email, or invoice action occurs once or twice.

来源

n8n lets you attach a separate error workflow that starts with the Error Trigger. Check both an error in a normal processing node and a failure in a trigger or activation step; the available error fields differ.

来源