Hi everyone! I recently upgraded Airbyte (self hos...
# replication-troubleshooting
j
Hi everyone! I recently upgraded Airbyte (self hosted), from 1.5.1 > 2.0.1 (helm chart versions 1.5.1 > 1.9.2), and now I'm seeing lots of syncs fail with 'transient errors':
Copy code
Warning from airbyte_platform: An internal transient Airbyte error has occurred. The sync should work fine on the next retry.
Has anyone run into this before? Or does anyone have any ideas how I can debug/fix it? Thanks.
i
Did it work on the next retry ?
if not, do a rollout restart on all deployments
j
Hey Iulian. It seems to work on a retry generally but then it keeps coming back at random across several connectors. I tried a rolling restart of the
temporal
and
worker
deployments but the issue persisted unfortunately
i
Usually there's an error in one of the services, that's why a rollout restart is best step here
on all deployments *
j
OK sure I'll give that a go, thanks.
Hmm still seeing the same transient errors after a rolling restart on all deployments. Anything else to try?
i
Check the logs of the Worker, workload api or workload launcher, the error must stem from there
increase the replicas for those, maybe it's a resource issue
j
I'll try that, thanks!
Thanks for the suggestions. For anyone else, it looks like the solution was setting the replicas for temporal to 1 (it was 2 previously): https://airbytehq.slack.com/archives/C01AHCD885S/p1772555520800749
👍 1