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
Using the StitchData FreshDesk integration. From the extraction logs:
Error persisting data for table "conversations": Record 6 did not conform to schema:
#/to_emails: #: no subschema matched out of the total 2 subschemas
#/to_emails: expected type: JSONArray, found: String
#/to_emails: expected: null, found: String
Using StitchData - I performed several full refreshes from FreshDesk without any problems then this problem showed up all of a sudden around 06:19am AEST March 26th. The ticket in question is a closed ticket that hasn't had any updates made to it. Below is the JSON response that appears to be causing the error. The only thing I can think of is the hyphen in the email address? I'm desperate for a fix or workaround, any help appreciated.
`[
{
"body":"
Responding via Email with meeting link to book in time.
",
"body_text":"Responding via Email with meeting link to book in time.",
"id":36008714812,
"incoming":false,
"private":true,
"user_id":36004641603,
"support_email":null,
"source":2,
"category":2,
"ticket_id":2172,
"to_emails":[
",
"body_text":"Client has signed and onboarding in progress. ",
"id":36013528556,
"incoming":false,
"private":true,
"user_id":36004641603,
"support_email":null,
"source":2,
"category":2,
"ticket_id":2172,
"to_emails":[
@LucasSheep@btrigger Can you please share a sample record in which to_email contains a string value?
Above shared records have to_email value in the list only.
Using the StitchData FreshDesk integration. From the extraction logs:
Error persisting data for table "conversations": Record 6 did not conform to schema:
#/to_emails: #: no subschema matched out of the total 2 subschemas
#/to_emails: expected type: JSONArray, found: String
#/to_emails: expected: null, found: String
Using StitchData - I performed several full refreshes from FreshDesk without any problems then this problem showed up all of a sudden around 06:19am AEST March 26th. The ticket in question is a closed ticket that hasn't had any updates made to it. Below is the JSON response that appears to be causing the error. The only thing I can think of is the hyphen in the email address? I'm desperate for a fix or workaround, any help appreciated.
`[
{
"body":"
"body_text":"Responding via Email with meeting link to book in time.",
"id":36008714812,
"incoming":false,
"private":true,
"user_id":36004641603,
"support_email":null,
"source":2,
"category":2,
"ticket_id":2172,
"to_emails":[
},
{
"body":"
"body_text":"Updated Hubspot ",
"id":36009995357,
"incoming":false,
"private":true,
"user_id":36004637235,
"support_email":null,
"source":2,
"category":2,
"ticket_id":2172,
"to_emails":[
"[email protected]"
],
"from_email":null,
"cc_emails":[
},
{
"body":"
"body_text":"Client has signed and onboarding in progress. ",
"id":36013528556,
"incoming":false,
"private":true,
"user_id":36004641603,
"support_email":null,
"source":2,
"category":2,
"ticket_id":2172,
"to_emails":[
}
]`
The text was updated successfully, but these errors were encountered: