Is there a limit of how many fields a Netlify Form can have. I have about 120 fields (… I know right…) and the build/deployment fails (just on Netlify) without an error. If I remove some most of the fields, it builds successfully. If I remove less of the fields it fails. Running these builds over and and over again to narrow it down is taking a long time and is killing my allotted minus.
Thanks! That link was EXACTLY what we were looking for; Our Support team can see that page on your site.
From it I sleuthed around a bit in our internal logs and it appears there is some kind of formatting error in /client-intake-form/index.html . This is the error we see:
</form>: unexpected 's-name48' after '[:equal, "'spouse'"]'
Perhaps you can hunt around there and see the problem?
Not at present, but you can tell “something” went wrong when you see this pattern in your logs:
5:18:05 PM: Starting post processing
5:18:05 PM: Post processing - HTML
5:18:11 PM: Starting post processing
5:18:11 PM: Post processing - HTML
5:18:12 PM: Starting post processing
5:18:12 PM: Post processing - HTML
5:18:13 PM: Starting post processing
5:18:13 PM: Post processing - HTML
5:18:14 PM: Starting post processing
5:18:14 PM: Post processing - HTML
…that something like this went wrong. We should only say Starting post processing once; we have 5 retries and then give up. IT is occasionally the case that something transient went wrong - we were deploying some component of our service while your assets were processing - and a second or third try will work - but if you see 5, we generally couldn’t succeed based on something in your code.
This is the first time I’ve seen an actual syntax error like this; it’s usually a reference in CSS to missing files or something like that, so congrats on finding a new error vector
Just in case it helps anyone else, turns out, I had a form input that ended up with some non-valid HTML. One of my inputs had a ' in the name field, and I bet the Netlify Form parser saw it and said NOOOOO (insert gif of Michael Scott here). This is the guilty suspect:
That would be a smart thing to do but also a challenge - our form handling service is looking for the name that your code sends, and just encoding it on our side wouldn’t affect how you send it. So this really is a fatal error - we can’t read the name of the field OR turn it into something that would “just work” for you based on the code you wrote.
But better error handling is definitely a thing we should (and are now) tracking as a feature request. We could at least tell you where the problem is since we do find out