Why is my n8n workflow stuck in waiting mode after form submission?

It sounds like your workflow is behaving as designed when using a Form Ending node that awaits a form submission. When you see the "Waiting for input" message along with the resume URL, n8n is pausing the workflow execution until the form at that URL is submitted. Here are a few things to check:

1. Production vs Testing Mode:
   Ensure that you’re using the Production URL for your form. In testing mode, some functionalities (like auto-populating query parameters or even automatic form submission flows) might not work as expected. When using production mode, the form should properly display and allow submissions.

2. Form Ending Configuration:
   If you want the user to see a confirmation or be redirected after filling the form, verify your Form Ending settings. You can choose between:

   • Show Completion Screen: Allows you to display a confirmation message.
   • Redirect to URL: Redirects the user to a specified URL after submission.

3. Workflow Resume:
   The displayed resume URL (the one in your error message) is generated to enable the workflow to continue once the form is submitted. Until the submission is received (either by clicking the link or via an external call), the workflow stays in the waiting state. This is the expected behavior for workflows that rely on user input via a form.

4. Automatic Submission (if applicable):
   If you’re expecting the form to be submitted automatically (for example, via custom logic or an external event), double-check that this process is triggering a proper HTTP request to the resume URL. Otherwise, the only way to resume the workflow will be through the manual submission via the provided link.

Review your Form Trigger and Form Ending configurations based on these points. The documentation explains that the Wait node or the Form Ending node will hold execution until the expected input is received, so if you want to resume without manual intervention, you may need to integrate a process that submits the form automatically (or use a different triggering mechanism such as a webhook).

If after reviewing these steps your issue persists, please verify your node’s configuration against the latest documentation to be sure nothing has changed in your version.