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 Maintenance

Understanding Migration Job Status

Learn what the different job statuses mean.

Written by Andrea Harvey

Updated at July 21st, 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 Available Job Statuses Filtering by Job Status Filtering by Failed Jobs

Overview

The job status indicates the current status of the job. It provides insight into which jobs are running, which jobs require attention, which jobs have completed their runs, etc. 

Available Job Statuses

Below is a list of the available job statuses and their meanings.

  • Idle: Indicates the job is not running. Select the job to view the next scheduled execution.
  • Paused: Indicates the job is currently on pause. While paused, the job will not run at the next scheduled time.
  • Running: Indicates the job is actively running and transferring content.
  • Complete: Indicates the job is done and has met a defined stop policy. A job with a complete status will not run again.
  • Cancelled: Indicates the job is in the process of being cancelled. The job will wrap up current processes during this status to ensure that the work is finished correctly.
  • Failed: Indicates the job audit log has captured one or more error entries.
  • Failed to Start: Indicates the job has failed to start correctly in the previous execution, which is typically the result of a misconfiguration or missing connection.
  • Queued: Indicates the job has reached it scheduled time and has been queued. It will be run based on its priority in the queue.
  • Awaiting user interaction: Indicates user interaction is required. (This is a transient status and cannot be used as a filter on the Job screen. See below.)
  • Resume: Indicates the job is in the process of being resumed after having been paused. (This is a transient status and cannot be used as a filter on the Job screen. See below.)
  • Success: Indicates the job was completed with no failures. (This is a transient status and cannot be used as a filter on the Job screen. See below.)

Filtering by Job Status

You can filter the Jobs grid by job status to display only jobs that are in a specific status or grouping. This is done by choosing Status in the Select filter list and then selecting the applicable status from the Select a value list. Most of the statuses have a direct correlation to the job status (as described in the previous section). The two "not" options in this list serve as a grouping for multiple statuses. They allow you to omit specific statuses.

  • Not Running: This lists all jobs that are not actively running–all jobs that do not have a status of Running.
  • Not Complete: This lists jobs that have not met the job stop policy–all jobs that do not have a status of Complete.

Filtering by Failed Jobs

When selecting Failed as a status, you have three additional filter options available.

  • All: This displays all jobs with the Failed and Failed to start statuses.
  • Failed: This displays only jobs where the job audit log captured one or more error entries.
  • Failed to start: This displays only jobs that failed to start correctly in the previous execution, which is typically the result of a misconfiguration or missing connection. 

 

 

 

migration job status

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Creating a Migration Job
  • Scheduling a Job
  • Adding a Job Stop Policy

Copyright 2025 – DryvIQ, Inc.

Knowledge Base Software powered by Helpjuice

Expand