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
  • API, CLI, and SDK Documentation
  • REST API Documentation
  • Jobs Using REST API
  • Job Management (REST API)

Configuring Started/Paused Status Using REST API

Learn how to configure job status using the DryvIQ REST API.

Written by Andrea Harvey

Updated at May 2nd, 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 Job JSON Example Started Paused PATCH/Modify Job JSON Example

Overview

DryvIQ supports creating jobs with a predefined “start” status through REST API configuration. You can create jobs with manual schedules that execute immediately or auto schedules that are paused until a user intervenes. Based on the chosen schedule method, DryvIQ offers two options for this setting: start and paused.

Job JSON Example

Started 

In the DryvIQ Platform user interface, the started status corresponds to the "Save and Run Job" option for manual jobs. This automatically starts jobs with a manual schedule. After initial execution, the manual schedule will continue to be preserved.

{
    "name": "Start Job - Manual - As started",
    "kind": "transfer",
    "transfer": {
        "audit_level": "trace",
        "transfer_type": "copy",
        "source": {
            "connection": {
                "id": "{{cloud_connection_source}}"
            },
            "target": {
                "path": "/sourcePath"
            }
        },
        "destination": {
            "connection": {
                "id": "{{cloud_connection_destination}}"
            },
            "target": {
                "path": "/destinationPath"
            }
        }
    },
    "schedule": {
        "mode": "manual"
    },
    "status": "start"
}

Paused

In the DryvIQ Platform user interface, a paused status corresponds to the "Start as Paused" for auto-schedule. This will pause the initial execution of the job until the user manually triggers it. Subsequent runs will continue on the regular specified schedule. The paused option is not preserved when making changes to the schedule. Should preservation be desired, each change will require this option.

When a job schedule of manual is configured, "paused" is not a valid option; only "start." A manual job does not have a true schedule

 
{
    "name": "Start Job - Auto- As paused",
    "kind": "transfer",
    "transfer": {
        "audit_level": "trace",
        "transfer_type": "copy",
        "source": {
            "connection": {
                "id": "{{cloud_connection_source}}"
            },
            "target": {
                "path": "/sourcePath"
            }
        },
        "destination": {
            "connection": {
                "id": "{{cloud_connection_destination}}"
            },
            "target": {
                "path": "/destinationPath"
            }
        }
    },
    "schedule": {
        "mode": "auto"
    },
    "status": "paused"
}

PATCH/Modify Job

The start/paused settings can also be applied to existing jobs using the PATCH options available through the REST API.

JSON Example

PATCH an existing job when changing the schedule.

{
    "kind": "transfer",
    "schedule": {
        "mode": "auto/manual"
    },
    "status": "paused/start"
}

 

api rest api job migration status started paused

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • DryvIQ Platform REST API Documentation
  • Connection Pools Using REST API
  • LDAP Account and Group Maps Using REST API

Copyright 2025 – DryvIQ, Inc.

Knowledge Base Software powered by Helpjuice

Expand