Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Migrations
  • Migration Jobs
  • Job Summary

Scheduling a Job

Learn how to add a schedule to a migration job to control when it runs.

Written by Andrea Harvey

Updated at June 25th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Insights
    Prebuilt Insights Custom Insights
  • Content
  • Accounts
  • Activity Log
  • Content Scans
  • Migrations
    Migration Jobs Migration Reports Maps Flagged Items Migration Tools
  • Connections
    Supported Platform Connections Creating Connections Connection Maintenance Connection Pools
  • Entity Types
    DryvIQ Available Entity Types Custom Entity Types Entity Type Maintenance
  • Action Sets
    Creating Action Sets Action Sets Maintenance
  • Settings
    License Performance Notifications Extensions Entity Types Settings Display Settings Configuration
  • API, CLI, and SDK Documentation
    REST API Documentation Command-line Interface SDK Development
  • POC Offering
  • Release Notes
+ More

Table of Contents

Overview Defining the Job Schedule Starting on Run job on Run job every First run start time Job stop time Maximum number of daily job runs At a specific time

Overview

A job schedule allows you to control when the job runs. The schedule automates job runs for you, eliminating the need for manual execution. The schedule can be set to determine both how often a job runs and when it should stop running (also known as the job stop policy). You set schedules at the end of the job creation process and have the option to edit schedules for jobs as well.

If you add a schedule to any of the mapping jobs (Folder Mapping, User Job Mapping, and Network Home Drive Mapping), the schedule is applied only to the child jobs. The parent job will still be set to run every six hours. If you need to edit the schedule for a parent job, you can do so once the job has been created. Similarly, child job schedules can be edited individually or in bulk after they are created. 

You can also set up a stop policy when creating the job schedule. See Job Stop Policy for more information.

 

Defining the Job Schedule

You can set the schedule for a job when you save the job on the Summary page of the job creation process. You have two options:

  • Save job: This launches the job scheduler so you can specify the details for the schedule you want to use.
  • Save job and run it right now: This triggers the job to start immediately. The job will use the default schedule settings. It will run every 15 mins after the last job execution completes, and the schedule will run every day.

 

Once you assign the job a name, select the Schedule job to run toggle to add the schedule details (or view the default schedule settings). This displays the schedule options. Use the options to set how and when you want the job to run. (See the information below for details about each schedule field.) Note that the default options set the job interval to 15 minutes and run the job daily. 

DryvIQ highly recommends that you name the job to make it easy to identify. If you leave the name blank and save the job, a default name will be assigned to the job using the source and destination connections. 

 

Starting on

Use this field to specify a starting date for the job; the first job will not run until this date. This allows you to create a job but not have it run until a later date. This would be useful, for example, if you are creating multiple jobs but want them to run in waves rather than all at once. You can create all the jobs simultaneously and set different starting dates. You only need to add a date to this field if you want the job to start running on a date later than the date you are creating the job. Leave this field blank if you want the job to start running immediately. This field can be used in combination with all other schedule fields. 

Run job on

Use this field to specify which days of the week you want the job to run. By default, all days are selected. You can clear days by clicking on a day in the list. The check mark in front of the day is removed, and the day no longer appears in the field above the list. Similarly, click on a day without a check mark to select the day to include it. Setting days can help create waves of jobs since you can set different jobs to run on alternating days, or it can be helpful to set jobs to run on days where activity is minimized (such as weekends). This field can be used in combination with all other schedule fields. 


Run job every

Use this option to set the job to run on a time interval. Specify the number and select if it is minutes, hours, or days. The time determines when the job will run after the previous job run completes, and not specific increments of time. For example, the default value is 15 minutes. This means the job will run 15 minutes after the previous job run completes.

This option can be used in combination with the Starting date and Run job on fields. It cannot be used in combination with the At a specific time option.

When you select this option, additional fields display that allow you to control the time frame for the job runs as well as the number of times the job will run per day. 

First run start time

Use this field to specify a start time for the first job run in the schedule. If no time is specified, the first job run will start at midnight. Specify the time using the format HH:MM XM.

Job stop time

Use this field to specify the time you want the job to stop running. The job will stop at this time if it is currently running. For example, if this field is set to 10:00 PM and the job is scheduled to start running at 9:45 PM, the job will begin as scheduled at 9:45 PM. If it is still running at 10:00 PM, it will stop regardless of the progress. If no time is specified, the last job run will start no later than midnight and will continue to run. Specify the time using the format HH:MM XM (10:00 AM, 10:00 PM, etc.).

Maximum number of daily job runs

Use this field to specify the number of times you want the job to run in a day. Once the job runs this many times, it will not run again until the next day.  


At a specific time

Use this option to set the job to run at a specific time of the day. This may be useful if you prefer jobs to run only during off-hours. You can specify the time here, and the job will run at that time for all the selected days. Specify the time using the format HH:MM XM.

This option can be used in combination with the Starting date and Run job on fields. It cannot be used in combination with the Run job every option. 

 

job schedule schedule job to run run job every run job at a specific time job stop time first run start time maximum job runs

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Scheduling a Job Using REST API
  • Adding a Job Stop Policy
  • Job Summary
  • Creating a Migration Job

Copyright 2025 – DryvIQ, Inc.

Knowledge Base Software powered by Helpjuice

Expand