Transformation Error - Stitch integration with Zendesk Chat

[ruchit12]

Hello, I have Zendesk chat integration to Snowflake Via Stitch, from past two days I am receiving an error and the data is not loaded. Can you please help me with it. The error I am receiving is: main - INFO Exit status is: Discovery succeeded. Tap failed with code 1 and error message: "Errors during transform". Target succeeded.
Error.txt

[vorpal56]

The fix is to change the webpath property in the catalog that's generated in discovery mode. This is likely due to some changes on Zendesk's part, though not entirely sure.

"webpath": {
    "type": ["null", "array"],
    "items": {
        "type": ["null", "object", "array"],
        "properties": {
            "timestamp": {
                "type": ["null", "string"],
                "format": "date-time"
            },
            "to": {
                "type": ["null", "string"]
            },
            "from": {
                "type": ["null", "string"]
            },
            "title": {
                "type": ["null", "string"]
            }
        },
        "items": {
            "type": ["null", "string", "integer"]
        },
        "additionalProperties": false
    }
}

[ruchit12]

Hello Anthony, Can we connect on a call as per your availability, to go over the problem and find the potential solutions for it. [cid:0d32f923-d74c-4909-b784-7da9c80a0877] Ruchit Mehta Data Analyst PICKUP [cid:9b9c02c1-4e53-4845-9110-f8e2e7e9d636] 6462554123 [cid:1e0bfd3c-72f4-4599-8a7c-33596b8e5207] ***@***.******@***.***> [cid:ac86323e-1270-4a22-a5d1-c7b7215ace8a] www.pickupnow.com<https://www.pickupnow.com/>

…

________________________________ From: Anthony Sukadil ***@***.***> Sent: Tuesday, March 15, 2022 4:41 PM To: singer-io/tap-zendesk-chat ***@***.***> Cc: Ruchit Mehta ***@***.***>; Author ***@***.***> Subject: Re: [singer-io/tap-zendesk-chat] Transformation Error - Stitch integration with Zendesk Chat (Issue #39) You don't often get email from ***@***.*** Learn why this is important<http://aka.ms/LearnAboutSenderIdentification> The fix is to change the webpath property in the catalog that's generated in discovery mode. This is likely due to some changes on Zendesk's part, though not entirely sure. "webpath": { "type": ["null", "array"], "items": { "type": ["null", "object", "array"], "properties": { "timestamp": { "type": ["null", "string"], "format": "date-time" }, "to": { "type": ["null", "string"] }, "from": { "type": ["null", "string"] }, "title": { "type": ["null", "string"] } }, "items": { "type": ["null", "string", "integer"] }, "additionalProperties": false } } — Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsinger-io%2Ftap-zendesk-chat%2Fissues%2F39%23issuecomment-1068499419&data=04%7C01%7Cruchit.mehta%40pickupnow.com%7C98b93a3de7d64bd0f73e08da06cc96da%7C589a0435190d4259969bc6ea82f65db5%7C1%7C0%7C637829773036776880%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=l3nnfpTSU9wTBdrjdBUEmDem3m5o4vGS7gZFGW%2FvSmE%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAX5ZBDULNIEWAVDYJZ6UUR3VAD7ZFANCNFSM5PH643XQ&data=04%7C01%7Cruchit.mehta%40pickupnow.com%7C98b93a3de7d64bd0f73e08da06cc96da%7C589a0435190d4259969bc6ea82f65db5%7C1%7C0%7C637829773036776880%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=oQNA%2Fo7I7RUq0dNDLU9qVIE4MUaEJk9t8mmDhvdSnPk%3D&reserved=0>. Triage notifications on the go with GitHub Mobile for iOS<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Cruchit.mehta%40pickupnow.com%7C98b93a3de7d64bd0f73e08da06cc96da%7C589a0435190d4259969bc6ea82f65db5%7C1%7C0%7C637829773036776880%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4V0m2be3MziXOLQ2prUrgYjgH6nxppmZRE7hQPzU6Z0%3D&reserved=0> or Android<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Cruchit.mehta%40pickupnow.com%7C98b93a3de7d64bd0f73e08da06cc96da%7C589a0435190d4259969bc6ea82f65db5%7C1%7C0%7C637829773036776880%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=d3VOcRMtEOc6K19W%2BK3t0W9PuIG%2B1qFkxBp1NvizTj8%3D&reserved=0>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[amyfeng-klaviyo]

We got the same error yesterday in stitch integration, any update on this?

[somethingmorerelevant]

Hi guys,
This issue is fixed in the following P.R #41
and released in version 0.3.2