"Next Form Page" keeps loading after Form trigger, no error shown

[Bill1212]

Describe the problem/error/question

Hi everyone,

I’m running into an issue while using Forms – the Next Form Page node keeps loading and doesn’t move forward.
I’ve tried looking for solutions in other posts but haven’t found anything that works. I’m wondering if there’s something wrong with how I set up my workflow.

I also found this recent post: Next Form Page node not working
, which seems to describe a similar issue. Does anyone know if it got resolved?

Thanks in advance for any help!

What is the error message (if any)?

no error shown

Please share your workflow

Share the output returned by the last node

Waiting for input
Execution will continue when form is submitted on https://op-n8n.vir000.com/form-waiting/576517

Information on your n8n setup

• n8n version: 1.123.6

• Database (default: SQLite): PostgreSQL

• n8n EXECUTIONS_PROCESS setting (default: own, main): default

• Running n8n via (Docker, npm, n8n cloud, desktop app): GCP K8s

• Operating system: Linux

[Anshul_Namdev]

Hey @Bill1212 Welcome to the n8n community!
I Guess this happens when you dont have any inputs in the next form page, which means you have an empty next form, add some inputs and it will work just fine and if you are using next form page as an END page you should consider the ‘Form Ending’ node. let me know if this helps!

[JohnHalex]

Hi @Bill1212 ,

Welcome to the community,

You should see this;

Form trigger always looping

Highlight: the part where he talks about Cloudflare Zero Trust.

Let me know if this helps!

[Bill1212]

Hey @Anshul_Namdev thanks for getting back to me!
In the second screenshot above, I’m using “Form Ending”, and the variables did receive the input.

[Bill1212]

Hello @JohnHalex ,
Thanks for sharing the article! I’ll take a look and see if it has any solutions that could help with my issue.

[Anshul_Namdev]

Thats strange, if you can share your workflow JSON that would really help as i will be able to see what data is being passed where, And for example as i was testing this it worked on this small workflow test i have made here:

[Bill1212]

Thanks for your help! Here’s the workflow JSON:

[Anshul_Namdev]

Hey @Bill1212 It works really well without me even touching it, what is causing you the error now?

[JohnHalex]

@Bill1212 it works fine.

[Bill1212]

I’ve been looking into the issue based on the article @JohnHalex shared, and so far it seems related to a CORS problem. I’m still working on troubleshooting it.

[JohnHalex]

Okay great, this should help. @Bill1212 let me know how it plays out.

[Bill1212]

Hi @JohnHalex , after adding some rules to the GCP Ingress YAML, the issue is now resolved.

Thanks a lot for your help!