Wait Node - Operation, On Form Submitted. Struggling (Bug/Nuance)

Describe the problem/error/question

Wait Node - Operation, On Form Submitted. I get the Wait operation but this very odd feature of the form operation has me struggling to use or understand its use case for users or what was n8n’s intention here? Was this before the forms option or something else? Documentation for n8n is pretty good, but almost always lacking to include examples and the mention of templates almost always do me no good as they never show, or have my use case, as is the case here and this is one such case an example would really help.

See below embeded workflow example and note:

  • The Flow is manually triggered and when tested all is good because the WAIT form pops up, ok cool but in the real world this would likely be triggered in a normal non UI based workflow or as a subflow so as per the disclaimer {{ $execution.resumeFormUrl }} is rendered at run time of the execution so GREAT… I tried sending the FORM workflow URL to my email so I could click the url to fill our the waiting form to be filled in, as this would complete the process
  • The result was the link in the email when clicked telling me the URL is no longer valid (also noting there is no way to Append n8n Attribution to OFF on the form :frowning: , but I digressed)
  • Since the form url {{ $execution.resumeFormUrl }} seams to NOT be accessable, after the fact and in a waiting state the flow will be in a forever wait state unless manually killed or the Timeout Workflow setting is enabled and configured.
  • Is this a bug, or can someone explain to me why this exists?

What is the error message (if any)?

No error message per say… just lots of unexpected behavior due to my ignorance on why or how one would use this in the real world. Why not use regular n8n forms

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.86.1
  • Database: SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): env not set
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm via nvm
  • Operating system: Win 11, 24H2 with CloudFlare Tunnel answering on auto. cnxlab. us so it acts like it is hosted and not localhost

With this now working, I can grok its use case now. This is a confirmed bug IMO or a poorly documented nuance…

{{$execution.resumeFormUrl}} does NOT include any configured “Webhook Suffix” that is configured in the wait node, so when you as the disclaimer says … send it else wheres BEFORE - the NUANCE is you MUST REMEMBER TO ALSO include/concatinate the “Webhook Suffix” MANUALLY (if you configured one…)

The fix looks like this

1 Like

Thanks for posting your workaround.

I see you also found the option to toggle off the attribution.

Not trying to add to your aggravation, but there’s also another part of this that could be better. The Webhook Suffix field can’t be set by expression. So, I’m adding this as a heads-up for for anyone who finds this thread later… you won’t be able to “factor it out” by using a Set/Edit Fields node to put the webhook suffix string in a common place. The webhook suffix string must be kept in synch manually by specifying it in two places. It’s not a show-stopper, but is annoying to anyone with a D.R.Y. programmer mindset.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.