The Workflow That Waited for a Human Who Never Came: Timeouts for Approval Steps in n8n

Description and use

In an n8n workflow, waiting for human approval can stall indefinitely. Introducing timeouts, escalations, and default actions bounds the wait, automatically handles overdue items, and enables queue metrics.

Problem

A human‑in‑the‑loop approval gate in an n8n workflow can stall indefinitely, causing a backlog of unapproved drafts without any node errors.

Outcome

Adding explicit timeouts, escalation, and default actions transformed an unbounded wait into a bounded, measurable process, preventing silent failures and enabling proactive monitoring.

Workflow

• Draft reply
• Park in review queue
• Wait for human approval
• If timeout occurs, trigger escalation step
• If escalation fails, execute default action

Evidence

The queue held forty unapproved drafts, the oldest three days old, and a customer asked why nobody had answered her.

Source

Nothing had failed. No node was red, no execution had errored.

Source

First, a timeout. Every approval step gets a deadline, and the deadline is a business decision, not a technical one.

Source

Second, an escalation. When the timeout hits, the item does not sit there. It moves: to a second approver, to a shared channel, to whoever is on call.

Source

Third, a default action. If nobody approves even after escalation, the workflow must still do something, and that something must be chosen in advance.

Source