Job running for hours after Airbyte update

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Job running for hours after updating to the latest Airbyte version when pulling data from Freshdesk.


Question

Hello Everyone,

I have been pulling data from Feshdesk without any hassle, the job gets done within a few minutes, recently (after we had some issues in Apr/May following switching to the latest Airbyte version), the job can run for the whole day, literally running for hours, averaging 6h 35mins.

What do I do please?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["job-running", "hours", "freshdesk-connector", "airbyte-update"]
2

These are not large tables as such, and I dropped some other tables from this connection.

This log excerpt is for a 6h 39mins job

3

As an experiment, try using new freshdesk version, and then switching back to a few versions behind, and compare their performance. If this is a connector regression, we’d be able to debug it that way.

4

I will try switching to older versions as the new version gives the same issue