Make your n8n workflows prove they did their job: six patterns for silent failures

Description and use

Patterns to detect silent failures in n8n: validate input rows, use a sentinel node for zero results, send heartbeat messages, and maintain a send log to prevent duplicates.

Problem

n8n workflows can finish green without performing any work, leading to silent failures such as zero rows, all rows filtered out, or duplicate messages.

Outcome

The six patterns convert silent failures into visible rows or messages, ensuring operators see when data is missing, filtered out, or duplicated.

Workflow

• Validate rows on entry and attach error reasons
• Use an IF node on row_valid to separate valid and invalid rows
• Add a sentinel node that emits an item when zero rows are returned
• Create a dedicated branch for empty data to send a heartbeat message
• Implement a send log in workflow staticData keyed by natural identifiers to prevent duplicate sends
• Prune old keys from the send log to keep it manageable

Evidence

A green execution in n8n means the nodes ran. It does not mean any work happened.

Source

The first Code node in most of my workflows does not transform anything. It validates.

Source

If the node before it returns zero items, there is nothing to evaluate, and the flow just stops there.

Source

Double sends come from double triggers: a manual rerun, a webhook retry, two overlapping schedules.

Source