Open mikebaldry-acu opened 9 months ago
Also running into this issue, seemingly out of nowhere. I've tried increasing the timeout
parameter for the trigger_sync
well beyond what the poll interval for the Airbyte server is set at. That seemed to help a bit, but still encountering frequent errors...
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.
Any updates on this issue, we are also facing this.
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: