@kapa.ai What does this error (reported via the UI) mean?

Setting attempt to FAILED because the workflow for this connection was restarted, and existing job state was cleaned.

This error message means that the Temporal workflow managing your connection was restarted, and as a result, the state of the currently running job attempt was cleared/cleaned up. When Airbyte's internal workflow engine (Temporal) restarts a connection's workflow, it cannot resume the previous job attempt mid-flight, so it marks that attempt as

FAILED

and cleans the job state. A few known causes for this: 1. Temporal server instability or multiple replicas: Running Temporal with more than one replica can cause conflicts that lead to workflow restarts and this error. One user resolved it by reducing Temporal's replica count to 1. [Temporal HA issue] 2. Missing or broken

ConnectionManagerWorkflow

: If Airbyte cannot find the workflow for a connection, it attempts to repair the state by creating a new workflow, which terminates any in-progress job. This has been observed after Airbyte upgrades. [MySQL data loss issue] What happens next? This is generally treated as a transient error — Airbyte's retry mechanism will automatically attempt the sync again. The retry backoff schedule is: [Sync Jobs docs] • 10 seconds after the 1st complete failure • 30 seconds after the 2nd • 90 seconds after the 3rd • 4 minutes 30 seconds after the 4th If the sync keeps failing with this error repeatedly, it may indicate an underlying infrastructure issue (e.g., Temporal instability, pod restarts, or an upgrade-related problem) that needs investigation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.