-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
N8N form node, freezes when clicking Next #11732
Comments
Hey @easydigi, We have created an internal ticket to look into this which we will be tracking as "GHC-441" |
Hey @easydigi, I am not able to reproduce this on 1.68.0, Were you able to hit the same issue with 1.68.0 as well? |
I am using version 1.68.0 in QUEUE mode. My environment is as follows: Works x2 |
After investigation, the issue is more easily reproduced when two Webhooks are set up, approximately 3 to 4 times out of every 10 attempts. The backend debug information is as follows: `webhook-2 | 2024-11-17T15:53:30.930Z | debug | Received webhook "POST" for path "4359201b-12ca-428b-af70-b2dca374f685" {"file":"live-webhooks.js","function":"executeWebhook"} n8n-worker-2 | 2024-11-17T15:53:30.972Z | debug | Start processing node "On form submission" {"node":"On form submission","workflowId":"wZRZe1a5AFP3WFb2","file":"LoggerProxy.js","function":"exports.debug"} n8n-worker-2 | 2024-11-17T15:53:30.972Z | debug | Running node "On form submission" started {"node":"On form submission","workflowId":"wZRZe1a5AFP3WFb2","file":"LoggerProxy.js","function":"exports.debug"} n8n-worker-2 | 2024-11-17T15:53:30.973Z | debug | Start processing node "Form" {"node":"Form","workflowId":"wZRZe1a5AFP3WFb2","file":"LoggerProxy.js","function":"exports.debug"} n8n-worker-2 | 2024-11-17T15:53:30.973Z | debug | Running node "Form" started {"node":"Form","workflowId":"wZRZe1a5AFP3WFb2","file":"LoggerProxy.js","function":"exports.debug"} n8n-worker-2 | 2024-11-17T15:53:30.974Z | debug | Save execution progress to database for execution ID 7754 {"executionId":"7754","nodeName":"Form","file":"save-execution-progress.js","function":"saveExecutionProgress"} n8n-worker-2 | 2024-11-17T15:53:30.985Z | info | Worker finished execution 7754 (job 5706) {"scopes":["scaling"],"executionId":"7754","jobId":"5706","file":"job-processor.js","function":"processJob"} The frontend received a 500 error, with the specific content as follows:
|
Below are the logs from a normal operation, which appear to be Webhook requests. Sometimes, these requests occur earlier than the Worker startup time. `webhook-2 | 2024-11-17T16:17:42.079Z | debug | Received webhook "GET" for path "4359201b-12ca-428b-af70-b2dca374f685" {"file":"live-webhooks.js","function":"executeWebhook"} n8n-worker-1 | 2024-11-17T16:17:56.312Z | debug | Running node "Form" started {"node":"Form","workflowId":"wZRZe1a5AFP3WFb2","file":"LoggerProxy.js","function":"exports.debug"} n8n-worker-1 | 2024-11-17T16:17:56.313Z | debug | Save execution progress to database for execution ID 7770 {"executionId":"7770","nodeName":"Form","file":"save-execution-progress.js","function":"saveExecutionProgress"} n8n-worker-1 | 2024-11-17T16:17:56.324Z | info | Worker finished execution 7770 (job 5722) {"scopes":["scaling"],"executionId":"7770","jobId":"5722","file":"job-processor.js","function":"processJob"} |
Hey @easydigi, In your set up do you have your load balancer set up to make sure all test requests only go to the main instance and the productions only go to the webhook workers? |
Yes, I used load balancing, and the Webhook uses a different domain name from the main instance: In the testing environment, the first page of the form is triggered through the main instance (using the domain name of the main instance). However, when redirecting to the form-waiting page, it automatically switches to the Webhook's domain name. Generally, this doesn't cause errors in the testing environment. In the production environment, it's confirmed that the same Webhook is used. In the production environment, if you don't immediately click "submit" on the first page but wait for a few seconds, the likelihood of an error occurring is significantly reduced. However, if you click submit immediately, the probability of an error increases greatly. Moreover, when one form-waiting page hasn't been clicked and more form-waiting pages are triggered, the probability of errors also increases. |
nginx -> traefik - > |
Bug Description
The form node behaves unstably when using the Next page functionality.
In test mode, it can switch pages, but it will freeze after testing for a period of time.
With the official link after the form is published, it almost always freezes when navigating.
The console occasionally reports errors:
To Reproduce
Expected behavior
After clicking submit, it can navigate to the next page.
Operating System
Docker
n8n Version
1.67.1~1.68.0
Node.js Version
20
Database
PostgreSQL
Execution mode
queue
The text was updated successfully, but these errors were encountered: