FivetranSensor missing syncs that complete before the sensor starts

[ANich]

Hi, thanks for the work on this provider.

We've noticed an issue for syncs that complete quickly after being started by the FivetranOperator. The FivetranSensor starts and begins polling after the sync has completed, so it continuously receives a scheduled state until another sync is triggered or it's marked as SUCCESS externally. This leads to long-running sensors (daily syncs for e.g.).

You should be able to reproduce this with a connector that syncs quickly and a sleep operator between the fivetran_sync_start and the fivetran_sync_wait.

We've solved this by (1) removing the fivetran_sync_start >> fivetran_sync_wait dependency between the operator and the sensor so the sensor task doesn't block the operator task (2) setting sensor priority > operator priority so the sensor starts shortly before the operator.

(Seems like something like #49 may solve this. Perhaps identifying syncs could as well?)

[PubChimps]

Thanks Alexander, we are solving this in the next release of the provider with XCOMs. I should have this release out and instructions on how to use the provider w/ XCOMs this week, I'll then post the instructions here and close this issue

[ANich]

Hi Nick, thanks for the response -- I'll keep an eye out for the next release then 👍

[PubChimps]

Please update to version 1.1.0 and see this example for how to catch short syncs