A Job is a scheduled operation that is used to perform a backup and comparison of your Project to the current instance in the Copia Server.

Creating a Job

To create a Job, navigate to the Jobs tab and press the Add a Job button.

General Settings

You should see a modal that allows you to configure your Job settings. Use the Project Name drop-down to select a Project to backup. The name of the chosen Project will be used to automatically populate the Job Name field (which can be modified if desired). The Timeout Duration refers to the amount of time given to a queued Job. You can modify it if more or less time is needed.


Scheduling allows you to set how often your Job should run. To turn on the scheduling feature, click the Schedule Job toggle.
The Daily option preselects weekdays. You can include weekends by enabling the Include Weekends checkbox. Use the Time selector to set the desired start time for the Job.
The Specific day(s) each week option allows you to choose which days of the week you prefer to perform a Project backup. Select which days of the week to run the Job and the set the time the Jobs should run with the Time selector.
If you prefer a more complex schedule, Copia provides the option to enter a "cron" schedule. Cron is a very simple but powerful scheduling format that is commonly used by system administrators. In this case, we provide a link to the site for syntax and examples to help you get started. Once you enter a correct cron schedule, a "plain text" interpretation will be displayed above the expression so you can validate your syntax.


Auto-Commit is a feature that allows you to backup, monitor, and be notified if your Devices change without any additional manual involvement. Auto-Commit will create a new branch to store this data so that it does not interfere with development. In this way, Auto-Commit provides easy disaster recovery and access to all machine updates.
When auto-commit is enabled, the device will be compared to the latest commit in the DeviceLink branch. If a difference is detected, a new commit will automatically be created, using the latest backup from the device. In this way the DeviceLink branch should always reflect the current state of the device.
The Auto-Commit feature is automatically enabled for new Jobs. By default, Auto-Commit is set to create a new branch with the DeviceLink/ProjectName syntax. If development on the Device is rare, or if you wish to use your own branch name, you can enter a new branch name into the New Branch Name field.
If a user chooses to disable Auto-Commit, they will need to manually create a Pull Request to update the branch that the project is stored on.

Managing Job History

Click on the Jobs tab and navigate to the Job History section. Your data is sortable by clicking the carets on the column headers.
There are 5 possible outcomes for a Job run -- each of which are shown as a chip in the Result column:
Job Outcome
Waiting for the Agent to start the Job
In Progress
Agent is currently performing the Job
🟢 Up to Date
Job was completed with no differences found
🟠 Modified
Job was completed with differences found
🔴 Failed
Job failed due to an error
🔴 Timed Out
Job took too long to be completed
A Job will usually time out when its supporting Agent encounters an issue. Typically, this will occur if multiple Jobs overlap, there is not a sufficiently long enough timeout value set, or your Agent experiences other connectivity issues.
For Jobs that are not pending or in process, you can see the differences by pressing the View Details button. This button will display the differences between the device and the commit that was used in determining the results.