I get this error far too often. Is there possibly some information about it so I can look up the error? In my opinion, after the error the completed form should at least be reopened; otherwise I can’t expect my team to deal with this. 
1 Like
Hi @Roman,
thanks a lot for reporting this issue!
In general, this error should only occur in a specific situation where the locally stored form draft gets out of sync with the current form definition. This can happen if a form was started earlier, not completed, and the form structure changed in the meantime, for example if fields were added or removed. In that case, the draft may still reference fields that no longer exist, which can lead to this error on submission.
However, since forms are still relatively new, it is also possible that this is an issue on our side.
If this happens again, it would be very helpful if you could open the browser inspector and capture the console logs in the console tab at the moment the error appears. A screenshot of the console output, together with the time, would allow us to correlate it with our backend logs and investigate the root cause much more effectively.
Thanks again for bringing this up!
Best regards
Leo
1 Like
This happens so frequently that I’ve noticed it. It’s not just occasional but really often. In the current process, I’m closing all open tabs to narrow down the issue a bit, but I haven’t been able to fully resolve it. I’ll collect the logs when I get the chance.
1 Like
I ran a test with a vehicle on the iPad we need for this process. I had to fill out three forms and did each one twice because my initial attempts failed. (There’s no console on the iPad with Safari.)
After that, I tried again on the laptop with Chrome, but that attempt also failed immediately.
Now that I’ve opened the console, I still can’t reproduce the error, even after eight attempts. I’m at my wits’ end. The process can’t be rolled out like this. 
How could we get to the bottom of the problem? Am I really the only one with this issue? 