Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Form Trigger does not wait in multi-form mode #11393

Closed
octionicsolutions opened this issue Oct 24, 2024 · 2 comments
Closed

Form Trigger does not wait in multi-form mode #11393

octionicsolutions opened this issue Oct 24, 2024 · 2 comments
Labels
in linear Issue or PR has been created in Linear for internal review Released

Comments

@octionicsolutions
Copy link

Bug Description

When having a node in between a Form Trigger and a New Form Page node, which takes longer than 2-3 seconds to load, the form reloads shortly after submission. The error happens both in test and production mode.
Also then the canvas shows, that the next form page is still waiting to be answered:
Screenshot 2024-10-24 at 3 26 34 PM
This also happens with other nodes than Wait. Like having 3 Notion nodes which gather many DB pages or an Execute Command node.

It does not occur if there is a Wait node or similar between two New Form Page nodes though.

To Reproduce

  1. Create a form trigger with any parameters
  2. add a wait node or similar which takes around 5 seconds to execute
  3. add a new form page node with any parameters
  4. Run the workflow in test mode
  5. Submit the initial form

After 2-3 seconds the error should show up in the browser and the workflow should be stuck at the last node.

Expected behavior

The form trigger should wait for the following nodes longer (minimum 30 seconds would be suitable) and maybe show an appropriate error + cancel the workflow execution if it takes too long.

Operating System

Ubuntu 24.04 LTS

n8n Version

1.65.0

Node.js Version

20.18.0

Database

PostgreSQL

Execution mode

main (default)

@Joffcom
Copy link
Member

Joffcom commented Oct 24, 2024

Hey @octionicsolutions,

We have created an internal ticket to look into this which we will be tracking as "GHC-344"

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label Oct 24, 2024
@janober
Copy link
Member

janober commented Oct 29, 2024

Fix got released with n8n@1.65.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in linear Issue or PR has been created in Linear for internal review Released
Projects
None yet
Development

No branches or pull requests

3 participants