Editing a Live Sync

Updated by Devinder Singh

Introduction

Once a sync is live, you can change its configuration without stopping it first. Byteline keeps the sync running on its current settings while you edit, then shows you exactly what saving will do before anything changes.

Use this when you need to:

  • Add, remove, or change field mappings
  • Adjust sync direction on specific fields
  • Update filters, matching keys, or table setup
  • Fix a mapping after records fail to sync

For first-time setup, see Data Sync - Getting Started. For how ongoing updates work after go-live, see Ongoing Sync (Real-Time & Scheduled Updates).

How to edit a live sync

  1. Open My Syncs in the Byteline console.
  2. Click the sync you want to change.
  3. Click Edit.

If the sync is running, Byteline creates a draft of your configuration. The live sync continues using its current settings until you save.

While you edit, a banner at the top confirms:

Editing a live sync

This sync will continue running while you make changes. Saved changes will apply after you save.

What happens while you edit

  • The sync keeps running on its existing configuration.
  • New changes in your apps keep syncing according to the current (not yet saved) setup.
  • Your edits are stored as a draft until you save or discard them.
  • If you leave editing without saving, you'll see a reminder that you have unsaved changes. The sync still runs on its current settings until you save.

You can click Resume editing to return to your draft and finish.

Saving your changes

When you finish editing a live sync, Byteline shows a save review screen instead of a preview run. A preview is useful when setting up a sync for the first time; for a live sync, what matters is how your changes will be applied.

Byteline analyzes your changes and tells you:

  • Whether the sync can keep running after save
  • Which table pairs are affected
  • Whether existing records need to be re-checked or re-imported

Then you choose how to save.

Your save options

Depending on what you changed, you'll see one of the following.

1. Save changes (applies to future sync activity)

When: Your change is a field mapping update that does not require restarting the sync.

What it does:

  • Saves your changes immediately.
  • The sync keeps running without stopping.
  • Future creates, updates, and deletes use the new mapping.
  • Already-synced records are not changed.

This is the recommended option for most field mapping tweaks when you only care about new activity going forward.

2. Update already-synced records

When: You changed field mappings on a sync that keeps matched records (not “Future data only” or “Historical only”).

What it does:

  • Saves your field mapping changes.
  • Re-applies the changed mappings to records this sync has already connected.
  • The sync does not stop or restart.
  • Matching, creating, and deleting records are not re-run — only the mapped fields you changed are updated.

Use this when you fixed a mapping and want that fix reflected on data that's already synced.

Note: This option is not available for:
- Future data only syncs (no record pairing is kept)
- Historical only syncs (one-time import, no ongoing pairing)

3. Stop and restart sync

When: Your change affects the sync setup in a way that requires listeners or existing data to be rebuilt.

What it does:

  • Saves your changes.
  • Stops and restarts the sync to apply them.
  • Rebuilds what the sync listens to and, where needed, re-checks existing records.

You'll see this when changes affect things like:

  • Table mappings (adding or removing tables)
  • Matching keys (when manually configured)
  • Record filters
  • Sync mode (e.g. existing + future data vs future only)
  • Field mapping changes that change the overall sync direction for a table (e.g. one-way → two-way)

The save review lists Tables affected and marks each as Restart needed or Re-import needed. Unaffected tables keep syncing until the restart completes.

What kind of change needs what?

Change

Typical result

Edit field mapping (same direction)

Save without stopping; optional update of already-synced records

Add or remove a field mapping

Save without stopping; optional update of already-synced records

Change option/value mapping on a field

Save without stopping; optional update of already-synced records

Change sync direction on fields (e.g. one-way → two-way at table level)

Stop and restart sync

Change matching keys (manual)

Stop and restart sync; may re-import existing data

Change record filters

Stop and restart sync; may re-import existing data

Add or remove a table pair

Stop and restart sync

Change sync mode

Stop and restart sync

Change app object type (e.g. different Webflow collection type)

Stop and restart sync

If you're unsure, complete your edits and review the save screen — Byteline tells you the required action before you commit.

After you save

Changes applied without restart

You'll see a confirmation such as:

Changes saved. Your sync picked them up without stopping.

If you chose Update already-synced records, you'll also see progress while existing records are updated. The sync stays live throughout.

Changes that need a restart

If your change requires a restart, the sync keeps running on the old configuration until you stop and start it. You'll see:

Your changes are saved and take effect on the next start. The sync keeps running on its current settings until then. Please stop and start the sync to apply them.

Click Stop & Restart Sync to apply the saved changes.

If the sync is already stopped when you save, you'll see:

Your changes are saved and take effect when you start this sync.

Start the sync when you're ready.

Discarding changes

On the save review screen, click Discard changes to throw away your draft and return to the live configuration. The running sync is unaffected.

Editing a stopped sync

If the sync is not live, Edit opens the same wizard, but there is no “editing live” banner and you'll get a normal preview on the last step (when applicable) rather than save review.

Common scenarios

Fix a field mapping after sync errors
  1. Open the sync and click Edit, or click Edit Field Mapping from the error banner.
  2. Update the mapping on the Choose & match your data step.
  3. On save review, choose:
    • Save changes — fix applies to new activity only, or
    • Update already-synced records — fix also updates records already connected by this sync.
Add a new mapped field to a live sync
  1. Edit the sync and add the field mapping.
  2. Save changes to apply it to future sync activity.
  3. Optionally choose Update already-synced records to populate the new field on existing matched records.
Change which records are included (filters)
  1. Edit the sync and update the filter.
  2. Save review will require Stop and restart sync because records excluded by the old filter were never synced and need to be re-evaluated.
  3. Stop and restart to apply.


How did we do?