Form ending error

[kanrun-digital]

Bug Description

hile attempting to transition between forms in an n8n workflow, an error prevents the form from loading as expected. The workflow structure follows a linear sequence where a form is triggered (On form submission), leading to subsequent forms (Form and Form1). However, the final form does not load properly, displaying an error message.

To Reproduce

Workflow Structure: The workflow comprises three main nodes:

On form submission (formTrigger node) - initiates upon form submission.
Form next - serves as an intermediary form in the sequence.
Form end - acts as the final completion form in the workflow.

Expected behavior

Problem Analysis:

Deactivation Issue: The error suggests that the workflow or a specific node might be inactive. Since the workflow's active setting is set to false, this may prevent form transitions from executing.
Non-Existent Node or Webhook: The webhook IDs tied to each form node might be incorrect or inactive. If any of the webhooks associated with the forms (webhookId) are missing or mismatched, the workflow might fail during transitions.

Operating System

Ubuntu 22

n8n Version

1.66.0

Node.js Version

18.60

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @kanrun-digital,

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

[Joffcom]

Can you share the env options you have set for your n8n instance and the workflow settings?

[kanrun-digital]

version: "3.8" volumes: n8n_app_data: n8n_db_data: qdrant_storage: ollama_storage: networks: n8n_default: services: postgres: image: postgres:16 restart: always environment: - POSTGRES_USER - POSTGRES_PASSWORD - POSTGRES_DB - POSTGRES_NON_ROOT_USER - POSTGRES_NON_ROOT_PASSWORD - EXECUTIONS_DATA_PRUNE=true volumes: - n8n_db_data:/var/lib/postgresql/data - ./init-data.sh:/docker-entrypoint-initdb.d/init-data.sh healthcheck: test: ['CMD-SHELL', 'pg_isready -h localhost -U ${POSTGRES_USER} -d ${POSTGRES_DB}'] interval: 5s timeout: 5s retries: 10 qdrant: image: qdrant/qdrant container_name: qdrant restart: unless-stopped volumes: - qdrant_storage:/qdrant/storage n8n: image: docker.n8n.io/n8nio/n8n:latest restart: always ports: - "5678:5678" links: - postgres environment: - DB_TYPE=postgresdb - DB_POSTGRESDB_HOST=postgres - DB_POSTGRESDB_PORT=5432 - DB_POSTGRESDB_DATABASE=${POSTGRES_DB} - DB_POSTGRESDB_USER=${POSTGRES_NON_ROOT_USER} - DB_POSTGRESDB_PASSWORD=${POSTGRES_NON_ROOT_PASSWORD} - NODE_ENV=production - WEBHOOK_URL=${DOMAIN} - GENERIC_TIMEZONE=${TIMEZONE} - EXECUTIONS_DATA_SAVE_ON_SUCCESS=none - EXECUTIONS_DATA_SAVE_MANUAL_EXECUTIONS=false - EXECUTIONS_DATA_PRUNE=true - N8N_SMTP_HOST=${N8N_SMTP_HOST} - N8N_SMTP_PORT=${N8N_SMTP_PORT} - N8N_SMTP_USER=${N8N_SMTP_USER} - N8N_SMTP_PASS=${N8N_SMTP_PASS} - N8N_SMTP_SENDER=${N8N_SMTP_SENDER} - N8N_SMTP_SSL=true - TZ=Europe/Kiev depends_on: postgres: condition: service_healthy volumes: - n8n_app_data:/home/node/.n8n - /n8n-local-files:/files ollama: image: ollama/ollama:latest container_name: ollama restart: unless-stopped volumes: - ollama_storage:/root/.ollama ollama-pull-phi3.5: image: ollama/ollama:latest container_name: ollama-pull-phi3.5 volumes: - ollama_storage:/root/.ollama entrypoint: /bin/sh command: - "-c" - "sleep 3; OLLAMA_HOST=ollama:11434 ollama pull phi3.5" depends_on: - ollama

…

On Sat, Nov 9, 2024 at 1:25 AM Jon ***@***.***> wrote: Can you share the env options you have set for your n8n instance and the workflow settings? — Reply to this email directly, view it on GitHub <#11661 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMO7OVC5HG6LYFOL4BAIT3TZ7VB5ZAVCNFSM6AAAAABROC5K7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRVHA4TIMRRGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Joffcom]

Hey @kanrun-digital

Can you remove EXECUTIONS_DATA_SAVE_ON_SUCCESS and let me know if that works? There is a known issue that will be fixed soon where if this is set to None the internal "wait" doesn't happen for some nodes.

[kanrun-digital]

Yes, it works!

…

On Mon, Nov 11, 2024 at 3:27 AM Jon ***@***.***> wrote: Hey @kanrun-digital <https://github.com/kanrun-digital> Can you remove EXECUTIONS_DATA_SAVE_ON_SUCCESS and let me know if that works? There is a known issue that will be fixed soon where if this is set to None the internal "wait" doesn't happen for some nodes. — Reply to this email directly, view it on GitHub <#11661 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMO7OVHTR2RCDBAGGAV4AED2AABWPAVCNFSM6AAAAABROC5K7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRXGA2TMOJUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[kanrun-digital]

[image: image.png]But Set the “Respond When” is not present in the new node n8n Form Trigger node version 2.2 (Latest) , in previous n8n Form Trigger node version 2.1 (Latest version: 2.2) is persist

…

On Mon, Nov 11, 2024 at 1:31 PM Vitalii Kovalchuk ***@***.***> wrote: Yes, it works! On Mon, Nov 11, 2024 at 3:27 AM Jon ***@***.***> wrote: > Hey @kanrun-digital <https://github.com/kanrun-digital> > > Can you remove EXECUTIONS_DATA_SAVE_ON_SUCCESS and let me know if that > works? There is a known issue that will be fixed soon where if this is set > to None the internal "wait" doesn't happen for some nodes. > > — > Reply to this email directly, view it on GitHub > <#11661 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/BMO7OVHTR2RCDBAGGAV4AED2AABWPAVCNFSM6AAAAABROC5K7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRXGA2TMOJUGU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[Joffcom]

Your image has not made it through.

[kanrun-digital]

there is no possibility to select the field at all and it gives an error 

[Joffcom]

Do you have a form ending node in your workflow?

[kanrun-digital]

It doesn't matter if you deleted the selection form in the update.



please find field “Respond When” parameter

[kanrun-digital]

and this field is present in the previous version of the trigger form.

[kanrun-digital]

and in the new version of node there is simply no such field

[kanrun-digital]

[kanrun-digital]

It's funny that it refers to something that cannot be chosen

[kanrun-digital]

Can you fix it, or should we wait to use the new version until you solve the problem?

[Joffcom]

Hey @kanrun-digital,

Sorry it looks like 2 different issues have been put into this rather than splitting it.

For the original issue we are aware of the problem which is down to one of the env options that you have set and with the second issue the "Respond to Webhook" node is no longer needed or used with a form trigger if you are doing a multi step form as we have a form ending page instead.

We will update the error to make that clearer and the documentation.

[kanrun-digital]

in this scenario, the final form is not shown, although the script says it was successful

[Joffcom]

Hey @kanrun-digital,

I would recommend creating a post on the support forum for that and including the full workflow, Looking at the output it looks like the node ran as the output is there but the expresion is invalid as $json.execution_id doesn't exist it looks to be $json.success as the only input which makes that a workflow issue not an application bug.