From ae246439b01a8fe34486dc8ea8de40708fdf472c Mon Sep 17 00:00:00 2001 From: Justin Ellingwood Date: Fri, 11 Oct 2024 14:16:37 +0100 Subject: [PATCH] Remove waiting execution limitation for webhook call (#2545) --- docs/integrations/builtin/core-nodes/n8n-nodes-base.wait.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.wait.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.wait.md index 59464a48b..f7ac4595a 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.wait.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-base.wait.md @@ -113,7 +113,6 @@ Set whether the workflow will automatically resume execution after a specific li There are some limitations to keep in mind when using On Webhook Call: * Partial executions of your workflow changes the `$resumeWebhookUrl`, so be sure that the node sending this URL to your desired third-party runs in the same execution as the Wait node. -* When testing your workflow using the Editor UI, you can't see the rest of the execution following the Wait node. To inspect the execution results, enable **Save Manual Executions** in your [Workflow settings](/workflows/settings/) so you can review the execution results there. ### On Form Submitted