Add and manage Job(s)

A Job represents a data set that is replicated from a source to a Destination of a Sync. Once a job is configured and saved, it is executed as defined by the job schedule.

A Sync is initiated to migrate data once it has configured Job(s) to manage the data migration/replication as needed. Each job oversees the data migration or replication between source and destination, while a Job Run represents a specific occurrence of this process. During a job run, the destination data is updated to reflect the migration/replication changes in the source.

To create a job and configure the sync completely, follow the steps below:

  1. Navigate to the Sync and + Add Job(s) to the top-right corner.

  1. Click + Add Job on the top right to add a job to the Sync.

  1. Configure jobs for the selected Sync and click Save Job to continue.

Run Schedule: All job configuration requires you to set its run schedule. The schedule is set based on the Cron format and runs in the set intervals. The default value for every run schedule is the same as its parent sync. You can override and customize it for Jobs.

A Cron expression field represents:

  • Minute (0 - 59)

  • Hour (0 - 23)

  • Day of the Month (1 - 31)

  • Month (1 - 12 or names: Jan, Feb, ..., Dec)

  • Day of the Week (0 - 6 or names: Sun, Mon, ..., Sat)

The expression follows a Unix-cron string format (* * * * * ) and specifies the schedule by the minute, hour, day of the month, month, and day of the week. A custom Cron is set for triggers where the job needs to run complex schedules.

Schedule the job run frequency either by selecting from the dropdown or entering a custom Cron.

Here, the Job run is scheduled to execute every minute of every hour, every day of the month, every month, and every day of the week, for every year.

  1. Once the Job is successfully saved, you can run and manage it. The Job overview is listed for each Sync by its name, schedule, duration, and run history.

Manage a Job

The jobs overview of a sync lists the current jobs. Each job is listed by their schedule, duration and run history report. Each run history is reported in vertical bars where you can check the added and changed rows during the job run when it started and its duration.

Users can manage a Job with the following actions:

  • Bulk actions on Jobs: Select bulk jobs to run them, update their run frequency, pause/resume, and duplicate jobs. Duplicating selected Jobs requires users to rename the selected jobs intended to duplicate to prevent any errors.


Duplicate Job(s) will share the original Job(s) Target DB Schema and Table name. Update the Target DB Schema and Table name in the duplicate Job(s) to prevent data duplication or loss.

  • Select a job to view its Job Logs and run it. Job logs are detailed records of the activities and events during a particular task or job execution. The logs capture important insights into the job's performance, including execution traces, status, and durations.

Select a job to edit, run or delete it. The Details list the job Run ID, status, last run time, duration, and rows that were added and changed during then. To the right, users can check the Live execution steps of the job.

You can also check the run details for each job run and the execution trace. The execution trace.

The execution trace of a job run refers to a detailed chronological record of the sequence of actions and events that occur during the execution of a specific job. The trace captures various aspects of the job run, including its status, overall status, insights into steps taken and their performances. This information is invaluable for monitoring performance, optimising job configurations, and ensuring successful and reliable data replication/migration between source and destination.

Last updated