- BrentwoodHalfMarathonAsked on April 29, 2017 at 06:31 AM
I use the Sendgrid app with all forms to automatically store the e-mail address in the Sendgrid contacts list. In our tests we find we consistently get the following error message with outlook.com e-mail accounts. No problem with gmail.com and others.
The outlook.com e-mail addresses are sent to Sendgrid contacts OK, but the error message appears.
If the upload below does not work the message is:-
SendGrid Adding recipient to list error!
Error encountered decoding JSON: Syntax error
The error message then block any confirmations being send despite the form entry being processed into Jotform OK.
- JotForm SupportNik_CAnswered on April 29, 2017 at 12:56 PM
Could you please confirm, when the Hotmail email is entered in the form and submitted the above error message is shown?
We'll wait for your response.
- BrentwoodHalfMarathonAnswered on April 30, 2017 at 11:15 AM
Outlook or MSN e-mail address is entered in the 'email' field in the 2018 Half Marathon Entry form. The error message occurs after the submit button is pressed and prevents return to the allocated web page.
It does however look like the record is saved OK and the e-mail address is entered OK in Sendgrid.
Tried again after re-setting the sendgrid app with all new API. Still got the same error message.
- JotForm SupportKevin_GAnswered on April 30, 2017 at 02:03 PM
Apologies for the inconvenience this may have caused to you.
I have integrated a sample form with SendGrid on my end and was able to replicate the issue, I can see it shows a JSON error, but submission is still saved and record is sent to SendGrid.
I will report it to our second level so our developers can further investigate it, we will let you know as soon as we receive any update about it.
- BrentwoodHalfMarathonAnswered on May 01, 2017 at 07:50 AM
Thanks for looking at the issue. I will get round the problem by using the Mailchimp integration. This seems to work fine with no error messages. Does the same job.
- JotForm SupportNeilVicenteAnswered on May 12, 2017 at 10:44 AM
This is now fixed.