Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mantrixflow.com/llms.txt

Use this file to discover all available pages before exploring further.

Incremental sync (and therefore sync state) is in beta. Use full sync for production pipelines until incremental sync graduates from beta.
Sync state is the checkpoint MantrixFlow uses to decide where the next incremental run should resume.

​
What sync state contains

For incremental sync, the state represents the latest successful cursor value — typically the highest updated_at or id processed in the last run.

​
What operators see today

In the standard workspace flow, operators mostly experience sync state indirectly through:
  • successful incremental runs only pulling rows newer than the last cursor value
  • run history showing whether the pipeline is progressing normally
The state itself is not exposed as a standard self-serve reset screen in the current product.

​
Practical example

Suppose Lighthouse Commerce runs an incremental sync on orders.updated_at every 15 minutes. After a successful run at 10:00, MantrixFlow stores the latest processed high-water mark. The 10:15 run uses that checkpoint so it reads only rows newer than the prior successful state.
  1. Check Run History first.
  2. Confirm whether the issue is source-side, transform-side, or destination-side.
  3. If the cursor or CDC assumptions changed, treat that as an operational recovery task instead of a casual reset.
  4. Re-run manually before restoring the schedule.