Reschedules are not treated

[FabioCoder]

We start the syncs in Fivetran mainly with the Airflow Operator of Fivetran and monitor them with the corresponding sensor. This way we can plan different DAGs depending on the syncs.

When a sync is rescheduled by the Fivetran engine, the sensor detects this. The status is also indicated on the Fivetran interface.

Extract from the Airflow log:
[2023-01-20, 03:03:11 CET] {fivetran.py:280} INFO - Connector "hepatitis_ligament": sync_state = rescheduled

Fivetran UI:

According to the entry on the interface, I expect the Fivetran engine to restart the sync at 3:07 AM. However, this was not the case. The sensor is now in a continuous loop until the next regular sync is triggered by AIrflow or someone intervenes manually.

I have already opened a Fivetran support ticket for a similar case. They said that the rescheduled sync in this case should not be triggered by the Fivetran engine but externally. In my opinion, the resync should be triggered by the Fivetran engine, otherwise it is a UI bug.

[LukaDevic]

Created internal ticket for reported issue.