Data Sync

Data Sync polls a provider on a schedule you set and stores the records it returns in a StackOne index. You don’t read that index directly. Deep Query searches and aggregates the stored records for you, without calling the provider. You configure Data Sync once per action on a Connector Profile. Every account on that profile is then synced automatically.

​

How it works

• You turn sync on for an action on a Connector Profile, and set how often it runs.
• StackOne creates one sync per Linked Account on that profile, for accounts already linked and any linked later.
• Each time a sync fires it is a run, which fetches records from the provider and writes them to the index.

​

Turn on sync for an action

​

Full and incremental runs

Most runs are incremental, because they’re cheap. Full runs happen on their own interval to catch what an incremental run structurally cannot.

​

Monitor syncs

Go to Accounts, open an account, and choose the Data Sync tab. Each synced action gets its own panel showing its cadence and when it next runs. Expand a sync to see its recent runs: whether each was full or incremental, how long it took, and how many records it created, updated, left unchanged, or deleted. The Enabled toggle is the one setting that’s per-account. Turn it off to stop syncing an action for this account without touching the profile or any other account. A sync shows Paused when the action, or sync for that action, is switched off on the Connector Profile. Nothing runs until it’s turned back on.

​

Data Sync events

A sync can also send an event to a webhook for every record a run creates, updates, or deletes, so you hear about changes without querying for them. See Data Sync Events.

​

Limits

The provider count means providers with at least one sync enabled, not actions. Syncing a second action on a provider you already sync costs nothing against it, and two Connector Profiles on the same provider count once. A connector can lower the per-run page and duration ceilings for an action that needs it, but never raise them. The page cap is usually hit first. In most cases, a run reaches 2,000 pages before it reaches 6 hours, so the duration ceiling is a backstop rather than the limit a run normally stops on. Turning on sync for an action fails if it would take the organization past 100 providers. The record and storage limits are checked as runs go, and a run that hits one stops early. Two more constraints are worth planning around rather than reading as numbers:

• Not every action can be synced. Actions that need parameters to run, such as fetching one record by ID, have no sync. See Turn on sync for an action.
• Deletions wait for a full run. Set Full re-sync to match how quickly you need them reflected.

Records expire once that retention window passes without a run. Any enabled sync refreshes them well inside it, so expiry matters mainly for a sync you disable and leave off: its records drop out, and reads against them start reporting nothing synced.

​

Runs that stop early

A run stops early when it reaches the page cap, when the provider returns the same page twice, or when the organization reaches its record or storage limit. What happens next depends on the run:

• A full run is held. Its records are discarded, the last complete sync stays readable, and no deletions are recorded. The next full run is attempted on the Full re-sync cadence. The run shows truncated or quota_exceeded.
• An incremental run keeps what it wrote, but its checkpoint doesn’t move, so the next run covers the same window again.

Neither sends events, so a day with an early-stopped run can have no events for that action.

​

Next steps