A sequence runs a set of related syncs in a fixed order, so a sync that depends on another only runs after that one finishes.
| Audience | Data teams orchestrating dependent syncs |
| Prerequisites | Two or more syncs, each set to the Manual schedule type. |
Why use a sequence
Use a sequence when one sync depends on another finishing first. For example, you might have two syncs that must run in order:
- Sync A creates a set of new contacts in your CRM.
- Sync B adds those contacts to their accounts.
Without a sequence, you'd schedule the two syncs far enough apart to hope the first finishes before the second starts. Sync duration varies, so that timing is never guaranteed. A sequence removes the guesswork: each sync starts only after the previous one finishes, and you decide per sync whether a failure should stop the rest.

Before you begin
- Have two or more syncs in your workspace. A sequence needs at least two syncs to order.
- Set each sync you'll add to the Manual schedule type. A sync's own schedule runs independently of any sequence, so a sync left on an interval or cron schedule runs both on that schedule and as part of the sequence.
Create a sequence
- Go to the Sequences page and click Create sequence.
- Click Add syncs and select the syncs to include. You can add more later.
- Reorder the syncs with the up and down arrows so they run in the order you need.
- Set each sync's failure behavior with its Terminate menu (see Control what happens when a sync fails).
- Name the sequence and set its schedule. A sequence supports the same schedule types as a sync.
- Save the sequence.

The final step is where you name the sequence and choose its schedule type.

Control what happens when a sync fails
Each sync in the sequence has a Terminate menu that decides whether that sync's outcome stops the rest of the sequence. Under Terminate sequence when, choose any combination of:
- Sync run has fatal errors — stop the sequence if the sync can't complete.
- Sync run has rejected rows — stop the sequence if the sync's rejected-row rate exceeds the Error rate threshold you set, as a percentage of the run's rows.
Leave both unchecked (the menu shows No) and the sequence continues to the next sync no matter how this one turns out.

When a sync terminates the sequence, the syncs after it don't run. Order your syncs so a failure stops the sequence before any dependent sync runs on incomplete data.
Run and monitor a sequence
Open a sequence from the Sequences page to reach its detail page, where you can:
- Enable or disable it.
- Run it manually.
- Review its run history.
- Edit its configuration or schedule.

To confirm a run did what you expected, click it to see each member sync's execution time and final state. A sync that terminated the sequence shows here, along with any syncs that were skipped as a result.