From abfcb757680297baaa45da94da11fe54c67bfdce Mon Sep 17 00:00:00 2001
From: mfsiega <93014743+mfsiega@users.noreply.github.com>
Date: Wed, 10 Dec 2025 15:39:20 +0100
Subject: [PATCH] Correct wait time cutoff (#4001)

---
 docs/2-0-breaking-changes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/2-0-breaking-changes.md b/docs/2-0-breaking-changes.md
index 640e43e00..7abcdebb1 100644
--- a/docs/2-0-breaking-changes.md
+++ b/docs/2-0-breaking-changes.md
@@ -16,7 +16,7 @@ The release of n8n 2.0 continues n8n's commitment to providing a secure, reliabl
 
 Previously, when an execution (parent) called a sub-execution (child) that contained a node that causes the sub-execution to enter the waiting state and the parent-execution is set up to wait for the sub-execution's completion, the parent-execution would receive incorrect results.
 
-Entering the waiting state would happen for example if the sub-execution contains a Wait node with a timeout higher than 60 seconds or a webhook call or a form submission, or a human-in-the-loop node, like the slack node.
+Entering the waiting state would happen for example if the sub-execution contains a Wait node with a timeout higher than 65 seconds or a webhook call or a form submission, or a human-in-the-loop node, like the slack node.
 
 Parent-Workflow:
 ![Parent-Workflow](/_images/v2/parentworkflow1.png)