-
Notifications
You must be signed in to change notification settings - Fork 5
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
Successful Airbyte syncs reporting as failed in Prefect, causing workflows to show as failed #64
Comments
Also running into this issue, seemingly out of nowhere. I've tried increasing the
|
We are also seeing this issue on our end! |
Any updates here? This happens quite a lot and is especially an issue for larger syncs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are experiencing intermittent "false negatives" (where an Airbyte sync succeeds but is reported as failed by the Prefect server) when triggering Airbyte connections in Prefect workflows. These failures occur more often when running multiple concurrent syncs, but aren't limited to only those times. The errors appear to be driven by timeouts, where the Airbyte server doesn't report status back to Prefect in a given timeframe.
Technical specs for the tools we're currently running:
The text was updated successfully, but these errors were encountered: