Skip to main content
This article is about Box Shuttle in the Admin Console. If you’re using legacy Box Shuttle, a standalone tool, see legacy migration guides.
You can schedule jobs to run at a given time and re-run them at configurable intervals.
migration-schedule-png

​
Schedule jobs

  1. Select Schedule using the the More Options menu.
  2. In the pop-up dialog, set the start date and time, as well as specify if the job will run periodically or one time only.  The Start Date and Start Time match the operating system’s time zone**.**
    You can also use the calendar to select the date.
  3. Define the conditions for running the job, based on the completion status of the previous job. 
    • No conditions: the job will run regardless if the preceding one was successfully completed or failed.
    • Successfully completed: The job will run only if the preceding one was completed successfully, without any errors.
    • Completed, possibly with errors: The job will run if the preceding one was completed, regardless of errors. The job won’t run if the preceding job was not completed or failed.
If you specify a condition for running a job, the scheduler will not run your job unless it meets those conditions. For example, if you select Successfully completed, and you stop the preceding job, the scheduler will not trigger the job because the preceding instance of that job did not successfully complete. You can check if the job meets the scheduler’s criteria to run by hovering over the scheduler pill when the job is not running.
Once scheduled, the job displays the schedule status, depending on the schedule settings:
    • Scheduled: the job was scheduled to run one time only.
    • Recurring: the job was scheduled to run periodically.
    • Paused: the job was paused and it won’t run until resumed.
When a scheduled job runs, admins and co-admins receive an email notification, confirming that the schedule works as expected. For details, see Manage Account Settings.

​
Manage scheduled jobs

You can manage the already scheduled jobs using the Scheduler menu.
migration-scheduler-png
The options allow you to pause, resume, edit, or cancel the schedule.

​
Scheduler limitations

There are certain limitations you need to have in mind when using the scheduler.

​
General

The scheduler may be unable to start a job for a number of reasons that are out of Shuttle’s control:
  • The job status may change to Invalid due to reconfiguration or changed source system credentials
  • Windows source system may disconnect.
Monitor your jobs periodically as they run to confirm that nothing prevents a job from starting.

​
Windows source system

Scheduler only runs one job for a Windows source system at a time. This ensures that each job has sufficient memory, CPU and other resources to transfer data to Box at optimal speeds. This does not affect cloud-sourced systems.
  • If you have a migration job already running for any reason, the scheduler will fail any additional jobs set to run while the first job is running.
  • If a job is already running when another job is scheduled to run, it will mark the second job as failed before it actually starts.
  • If you have two jobs scheduled for a Windows source system at the same time, it will run the first one and fail the second one.
When the job fails, it will receive the Failed  status on the dashboard. Because the job fails before it even starts, it won’t have any job history, so you won’t see the job failure in the report section of Shuttle. The only place that the job failure will be listed is in the job card:
failed-job-png
If you go into Run History for the job, you will still see any previous runs of the job, but you will not see any details related to the scheduled job failure other than the Failed tag in the job header, because the job did not actually run.