Skip to main content
Sync state is the checkpoint Arcyria saves after a successful Incremental run. The runner extracts state before deleting temporary staging files. The platform persists that checkpoint so later Incremental runs can resume.

​
When state matters

State matters when:
  • a destination uses INCREMENTAL
  • a schedule is active
  • you change the replication key
  • you are investigating missing or duplicated rows

​
Reset or backfill a stream

Open Source, then Options on an Incremental stream:
  • Reset state reloads the stream from the beginning on its next run.
  • Backfill from value re-reads rows whose cursor is at or after the value you enter, for example 2024-01-01T00:00:00Z or 1000.
Both actions ask for confirmation and are refused while a run is active. Destination rows are upserted, so re-read rows do not duplicate. Changing a stream’s cursor column also restarts that stream from a fresh load.

​
Operational guidance

  • Do not change replication keys casually after a pipeline is running.
  • Validate a manual run after any sync-mode or replication-key change.
  • Treat state resets as operational recovery work.
Full Table runs do not depend on checkpoint state for scheduling because they are manual-only in the current app.