-
Notifications
You must be signed in to change notification settings - Fork 18
Fivetran Sensor shows incorrect sync status #71
Comments
Any updates on this?
|
Any updates on this? Bing logs |
Recommend to follow this doc as a guide and use FivetranOperator + FivetranSensor in the same dag. Use the xcom so that the sensor is looking for the correct sync event that is passed to the xcom by FivetranOperator. https://www.fivetran.com/blog/orchestrating-elt-in-airflow-catching-every-sync-with-xcom Guessing that the |
I just saw this. Will look into it and close the issue if that serves the purpose. Thanks! |
I implemented this solution and it it's been working fine for all situations except for reschedules. |
Any updates? |
There is an issue that we have been seeing every 2-3 weeks now across multiple kinds of connectors
The issue is:
Sometimes, the sync status from the the Fivetran Sensor is not correctly updated even if the sync status is updated in the UI dashboard.
Eg: Let's say when a sync is triggered, the sync status in the UI dashboard would change to
scheduled
, then tosyncing
and then tosynced
. All within a few mins.But the sync status from the sensor would still remain stuck at
scheduled
. We have a task timeout of 1 hour. So, after one hour the task automatically fails. Then we go look in the UI dashboard and see that everything is normal, there were not errors during the syncfivetran_sync_google_ads_fivetran_wait_for_google_ads_20220701_sync_2023-02-09T07_45_00+00_00_1 (1).log
Can you please let us know why is there discrepancy in the status returned by the APi response via the sensor and the status in the UI dashboard?
I'm attaching logs from our Airflow Task for clarity
The text was updated successfully, but these errors were encountered: