-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FivetranOperator fails when a connector goes to rescheduled
state
#107
Comments
Hi @SouravBhowmikDE, would you be interested in submitting a fix? I’d be happy to review and merge it. |
Hi @pankajastro Sure, I will give this a try in a few days. I have never done this before. |
If you do this, please take care to not have the operator continue waiting if the connector is set to manual schedule mode. For connectors with a manual schedule, the IMO Fivetran should never have connectors with a manual schedule end in a |
OverviewI'm not sure that failing is correct @sean-rose . There is already logic in place to wait and trigger the sync again after a configurable amount of time (
My theoryThe undesirable behavior is that the operator is hitting an unhandled exception
The TriggerEvent error is then passed back to the operator and executing this line:
Deeper dive: The synchronous If, in any case the
This case occurs here when the
see this excerpt:
Edit: The problem actually appears to be that The root cause here is that by overriding the My suggestionSuggested fix:
@pankajastro Do you have any thoughts? Sample PR is up - let me know what you think |
Hi
We have a Google connector that goes to
rescheduled
state every now and then.And whenever the connector that goes to
rescheduled
state, the FivetranOperator Airflow task always fails.It seems that the FivetranOperator has a bug and it does not handle the
rescheduled
state correctly.Can someone please fix the issue asap.
Below is the logs from the failed FivetranOperator Airflow task:
The text was updated successfully, but these errors were encountered: