Form Node bugs (?)

Describe the problem/error/question

There seem to be a few bugs in the Form node:

1/ Timeout is not working
2/ Timezone/Localization is not working
Screenshot 2025-04-03 at 23.23.11
Screenshot 2025-04-03 at 23.23.23
Screenshot 2025-04-03 at 23.23.33

Cf pics:

  • TimeZone is set to Europe/Brussels, but still the date format is US (MM-DD-YYYY] instead of [DD-MM-YYYY], what it should be. n8n is wrongly coding it as 04/18/2025 (MM-DD-YYYY].
    And as shown, I did check “Use WF Timezone”.
  • Timeout : set to 15 mins but in practice the Node stops listening before I have a few form fields filled out. (under 1 minute! Really annoying!) I can never even reach the Submit button.

Information on your n8n setup

  • n8n version: → 1.84.33
  • Database (default: SQLite): → PostGress
  • n8n EXECUTIONS_PROCESS setting (default: own, main): → own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): → via Docker on render.com
  • Operating system: → Ubuntu

Hi I have just checked your settings locally and they work fine including date and timeout. So maybe you browser or system settings interfere, hard to tell like this.

You might want to try and upgrade to 1.85.4 to resolve any issues.

Hi Sebas! Thanks but… I’m working on a Mac so all my apps conform to the system wide settings, the scenario you envision is highly unlikely. (in Safari’s settings you can’t even override those system settings).
Yet, from a naughty desire to prove you wrong, I will test it in Chrome as well today and let you know haha.
On the version: I always automatically have the last stable version deployed so if the version you mention is stable release I should be running it already.

Hi Sebas,

An update:
As promised,

  • I checked the version (is 1.85.4 - so I reported that wrong in my first post, shoudl have checked. But: I DO have the latest stable version deployed)
  • I also tested in Chrome

There’s good and bad news:
The good news is: it WAS a Safari issue. An Apple bug. As in my system settings I did have my date format set correctly (see screenshot): (dd-MM-YYYY @Date Format)

Yet in Chrome the date showed right… so I knew something was off.
There’s an option in OSX to set App-specific overrides and only when I set that to EU, it showed correctly in Safari. (so I reported this bug to Apple)

Unfortunately…

  • Even if my TimeOut is set to 15 mins, the WF gives up after about 2 mins already. So that is definitely a bug, also in the latest stable release.
1 Like

Hey there, under the hood, the Form input is using the default JS input. So if there is a problem for localization, it is either from the way <input> is handling localization or something with the machine being used

Yeah, on the localization issue, I believe Apple messed up a bit - so I filed a bug with them.
Yet the test workflows ending prematurely (and despite being explicitly set otherwise) is on n8n I am afraid.

Do you mind sending in your workflow? Also, if you could also send a video of the execution not workin, that would be a super helpful bonus. Thanks

Hi danougill - thanks for caring.
In the upload: sure but… I do I do that? I just tried and it would just allow me to upload images (of certain extensions) and hyperlinks…
On the video: nothing to see, other than while I am trying to enter 10 fields (you will see in eth submission form trigger) the "Listening " often stops after a mere 10 - 15 seconds. The weird part is: not always. So I’m not sure what is in play there. Is something interfering it? (not that I know and for sure not of my part).

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.