Hi @kapa.ai When you cancel a sync is there a connection state saved so that you can catchup on the next sync ?

Yes, in most cases Airbyte can catch up on the next sync, but the details depend on how the sync stops: • Incremental syncs use state (cursor) to resume: Airbyte sources emit state (cursor values) during a sync so that the next run can continue from the last saved point instead of starting over. This is what enables “free backfill” after downtime or failures.[State & checkpointing; Backfill with S3] • State is checkpointed mid‑sync for incremental streams: For incremental streams, state is saved after a stream slice is fully read or when the number of records reaches the

state_checkpoint_interval

. This means that even if a sync doesn’t complete, the next run can start from the last successful checkpoint instead of from the very beginning of the stream.[Incremental append behavior; State & checkpointing] • Canceled syncs specifically: The release notes mention that canceled syncs no longer immediately rerun; they wait until the next scheduled sync. They do not explicitly state a special behavior for state on manual cancel, but given the general checkpointing behavior above, any state that was already checkpointed before you hit “Cancel” will be used on the next run.[Airbyte 1.4 bug fixes] Because the docs do not explicitly say “cancel always saves state at the moment of cancel,” the safest assumption is: • You will catch up from the last successfully checkpointed state (not necessarily the exact point of cancellation). • To verify or adjust what will be read next, you can inspect the Connection State in the UI under Connection → Settings → Advanced and, if needed, carefully edit it to change where the next incremental sync starts.[Manage connection state] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.