In some cases, Umbraco form entries are missing in our umbraco backoffice. It doesn't happen every time, only sporadically. However, emails are sent out in accordance to the described workflow, even when the form entries are missing in the backoffice. We couldn't detect any pattern in particular in the cases where form entries are missing. Furthermore, nothing is logged in the umbraco logs, which doesn't really help to find the cause.
We aren't sure what to do and I don't really have much information to supply. Has anyone ever experienced an issue like this?
I have had similar issues over the years with Umbraco Forms, in some circumstances, it's turned out to be the data filled in by the user, that have had an anomaly in their data (weird character or missing field) that has caused the data not to be stored, but somehow the email to be sent.
What I'll often do is take the data in an email and re-enter it exactly into the form, just to rule out that it's the actual data causing the issue.
When the concept of 'consent' was added for GDPR, there was a whole lot of confusion on some existing forms not consenting for people's data to be stored.
I've had a schema mismatch on the Umbraco Forms database tables, not allowing insertions (but you are getting some so it's unlikely to be this)
And then I've had timeouts, access to the SQL server is locked, or there are so many records in Umbraco Forms that the insertion times out, but I'd expect you to be able to see some detail in the logs when this happens
(might be worth setting the log level to debug, if you haven't already, to see if there is more detail)
And I've had custom workflow steps that nobody quite knew about, that was meant to delete old entries after a time period, but weren't accounting for different date formats and so was deleting recent records too.
And a workflow that was deleting possible 'spam'... that was overzealous.
Anyway, not super helpful :-( hopefully the extra logging level will reveal more...
I have actually found out, that my issue was caused by too much data as you had mentioned. My assumption is that the amount of data was too long to be saved into the UFRecordDataString table, which in our setup only allows values with a max length of 255 letters. Our solution most likely will be to recreate the table with a larger datatype.
Umbraco form entries missing.
Hello everyone,
In some cases, Umbraco form entries are missing in our umbraco backoffice. It doesn't happen every time, only sporadically. However, emails are sent out in accordance to the described workflow, even when the form entries are missing in the backoffice. We couldn't detect any pattern in particular in the cases where form entries are missing. Furthermore, nothing is logged in the umbraco logs, which doesn't really help to find the cause.
We aren't sure what to do and I don't really have much information to supply. Has anyone ever experienced an issue like this?
Thanks in advance.
Kind regards, Melissa
Hi Melissa
I have had similar issues over the years with Umbraco Forms, in some circumstances, it's turned out to be the data filled in by the user, that have had an anomaly in their data (weird character or missing field) that has caused the data not to be stored, but somehow the email to be sent.
What I'll often do is take the data in an email and re-enter it exactly into the form, just to rule out that it's the actual data causing the issue.
When the concept of 'consent' was added for GDPR, there was a whole lot of confusion on some existing forms not consenting for people's data to be stored.
I've had a schema mismatch on the Umbraco Forms database tables, not allowing insertions (but you are getting some so it's unlikely to be this)
And then I've had timeouts, access to the SQL server is locked, or there are so many records in Umbraco Forms that the insertion times out, but I'd expect you to be able to see some detail in the logs when this happens
(might be worth setting the log level to debug, if you haven't already, to see if there is more detail)
And I've had custom workflow steps that nobody quite knew about, that was meant to delete old entries after a time period, but weren't accounting for different date formats and so was deleting recent records too.
And a workflow that was deleting possible 'spam'... that was overzealous.
Anyway, not super helpful :-( hopefully the extra logging level will reveal more...
regards
Marc
Hello Marc and thanks for your reply.
I have actually found out, that my issue was caused by too much data as you had mentioned. My assumption is that the amount of data was too long to be saved into the UFRecordDataString table, which in our setup only allows values with a max length of 255 letters. Our solution most likely will be to recreate the table with a larger datatype.
Thanks for your help!
is working on a reply...