I created an example webhook where I have 3 nodes of type ‘wait’, after the execution of the second node wait or wait longer than 1 minutes the node does not execute or does not continue with the execution.
Anything less than 65 seconds will keep the execution running (in memory) and resume after the period expires.
If you set a node to wait for more than 65 seconds, n8n will “stop” the execution (putting the workflow back in the database) and resuming it later.
This means the execution is offloaded, saved in the database until the time to continue approaches, and then n8n picks it up again.
Given it’s a webhook trigger, the http request will simply respond as soon as you get to the second node with whatever data n8n has. The execution will continue, but the http request will be responded and closed already by this time, since the execution has been put to “sleep”.