Understanding Sync Jobs in Data Bridge

Becky Hackman

Modified on: Fri, 16 Oct, 2026 at 1:32 PM

Overview

A sync job is a defined sync between your source system and Onefile. The Data Bridge agent runs a job by its ID, reading from your database and pushing records to Onefile. You can preview a job, rehearse it with a dry run, run it live, and schedule it to run on a cadence that suits you.

User Roles

This feature can be used by:

Centre Manager

How a Sync Job Runs

Preview: DataBridgeAgent.exe preview --job <id> shows exactly what would be extracted and how it maps, reading only and writing nothing.
Dry run: DataBridgeAgent.exe sync --job <id> --dry-run runs the whole pipeline without reporting to the portal or writing to Onefile.
Live run: DataBridgeAgent.exe sync --job <id> runs the sync for real.
Schedule: use Windows Task Scheduler to run the live command on your chosen cadence.

⚠️ Important: Each job is protected by a lock, so two runs of the same job can never overlap — a second run exits with code 6. If you schedule a job, make sure it can't be scheduled to overlap itself.

Active and Inactive Jobs

A job can be switched off in the portal. If you run an inactive job, nothing is read or written and the agent exits with code 8.

Tips & Notes

Always preview or dry-run a job before its first live run, so you can see what will be sent without writing anything.
If you sync from more than one database, run one agent per database — each job runs under the agent configured for its source database.

Terminology

The terminology used in this article may differ depending on your Centre's configuration.

Need Help?

If you need assistance, please contact Onefile Support or your internal support team.