I encountered an issue with wait node. So in my workflow I have a Gmail node that sends link ($execution.resumeFormUrl) to wait node form. In the wait node I have set Respond When - Form is submitted, but instead of seeing response recorded screen, the submit button keeps loading until the workflow finishes, since in next steps I still have to use some other user input, this sometimes can take days. Please help.
I cannot share my workflow as it contains sensitive information. But it looks like this. The issue happens with Wait4 node.
There are some limitations as to how long a workflow can take and how long Wait can wait.
You probably can fix this as you have the full control over your instance of n8n.
How does Wait node help to handle scenarios with a timeout on the userās side? What if they never follow up?
Iād apply a different strategy. Do not know much about your use case, but user flow state registry might be a solution. This introduces some overheads and more complicated business logic but you will have more control over the process flow.
I understand the general limitations around workflow execution time and the risks of users not following up ā and I do agree a state registry system could be a more scalable solution for some use cases. However, thatās not really the issue Iām facing here.
Let me clarify the problem a bit more:
In my current setup, the workflow sends a Gmail message with the $execution.resumeFormUrl (from the Wait node). The Wait node is configured with āRespond When: Form Is Submitted.ā So, naturally, I expect that when the user opens the form and clicks Submit, they should immediately see the āResponse recordedā screen.
This used to work perfectly ā the moment the form was submitted, the user would see the confirmation screen, even though the rest of the workflow might still be running in the background.
Now, the form just hangs on submission ā the Submit button shows a spinner and doesnāt complete until the entire workflow finishes. This defeats the purpose of having āRespond When: Form Is Submittedā and results in a terrible user experience (especially for forms that shouldnāt wait on future steps to show a response).
Also, just to clarify ā Iām currently testing the workflow manually, so thereās no delay or user follow-up gap involved. The issue happens immediately during testing, with the workflow being executed end-to-end without any idle time.
Iām running a self-hosted instance with full control over execution settings (including timeouts), and this is definitely a new behavior, likely introduced in a recent version. So Iām wondering if anyone else has encountered this regression or knows of a fix.
Might be a bug. As much as I would be willing to look into, but I do not feel comfortable investing effort into reproduction of the case.
Maybe you could create and share the minimalistic workflow to play with?
Surely, I can use my own credentials for gmail et al
I tried to recreate the workflow, so basically if there is no other nodes between Wait and Gmail (sendAndWait) then it all works, but if I insert any other nodes between it freezes.
I am not sure what was your intention as to the approval flow (may be you wanted a different user to accomplish the approval/rejection?), but Form Ending kicks in before anything else past Next Form Page node.
Here it works, to me predictably and as expected.
Alternative solution (just moved the Form Ending to be executed later than anything before or above it). This makes Form Ending approached by n8n when the branch above gets accomplished.
n8n peculiar order of execution is a documented feature.
Iād leave conducting a comprehensive testing of either of proposals above to you.
If your issue is resolved, please mark this post as a Solution.
This is not really a solution, because in my use case the input comes from 3-4 different people. I need the form ending to be first to shown because the first person who fills all the data needs to see thank you screen as he does not need to do anything else after this. Then the workflow moves on with other people. I will look at your ideas and find some middle ground. Also I noticed that if I remove the next wait node in workflow (edit branch), although that branch does not execute, the issue is gone. So in my opinion definitely a bug. Thanks for your help.
workflow1 (parent one). Make sure you have disabled the switch Wait for Sub Workflow Completion in the Execute Workflow node (you can also pass any parameters in your sub workflow, if you need, by setting the execute worklfow trigger options to āDefine using Fields belowā)
Solution.