You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
StrongGrid is sometimes unable to parse the data returned by the api.sendgrid.com/v3/marketing/contacts endpoint because of the date format used for the created_at and updated_at fields but this problem is not consistent. Sometimes we are able to parse the data without any problems and sometimes it fails with the following exception: The JSON value is not in a supported DateTime format.
This is caused by the fact that the endpoint sometimes returns data such as this: "updated_at":"2024-03-21 16:21:30 +0000 UTC" rather than the expect standard format which looks like this: 2024-03-21T16:21:30Z. The System.Text.Json deserializer does not handle the custom format and therefore throws an exception when we attempt to parse the JSON data.
To be clear: I want to insist that this problem is not consistent because the endpoint does not consistently use this custom format. It appears that SendGrid intermittently switches between the expected format and the custom format.
The text was updated successfully, but these errors were encountered:
StrongGrid is sometimes unable to parse the data returned by the api.sendgrid.com/v3/marketing/contacts endpoint because of the date format used for the
created_at
andupdated_at
fields but this problem is not consistent. Sometimes we are able to parse the data without any problems and sometimes it fails with the following exception:The JSON value is not in a supported DateTime format
.This is caused by the fact that the endpoint sometimes returns data such as this:
"updated_at":"2024-03-21 16:21:30 +0000 UTC"
rather than the expect standard format which looks like this:2024-03-21T16:21:30Z
. The System.Text.Json deserializer does not handle the custom format and therefore throws an exception when we attempt to parse the JSON data.To be clear: I want to insist that this problem is not consistent because the endpoint does not consistently use this custom format. It appears that SendGrid intermittently switches between the expected format and the custom format.
The text was updated successfully, but these errors were encountered: