# Deploying Workflows

**Last Updated On**: 21 Apr 2026  
**6 minutes read**

## Overview

Once a workflow is created in DEX Manager Plus, it must be deployed to target device groups to take effect. The Deployments allows you to configure how and where workflows are executed—whether immediately or on a schedule. You can also monitor deployment progress, track device-level outcomes, and manage rollouts across your environment.

This page outlines the steps to deploy a workflow and best practices for safe, effective execution.

## Why Deployment Matters

| Functionality | Value |
|---|---|
| Controlled Execution | Define when and where workflows run. |
| Selective Targeting | Deploy only to relevant device groups. |
| Flexible Scheduling | Run immediately or schedule for later execution. |
| Execution Monitoring | Track status, outcomes, and error logs. |

**Note:** Only workflows that have been saved with **Active** status can be selected for deployment.

## Prerequisites

- At least one workflow must be created and saved.
- You must have permission to create deployments. Role is Workflow
- Custom Groups that is going to be included in target has to be created. Refer [document](https://www.manageengine.com/digital-employee-experience/help/custom-groups/custom-groups-overview.html) for detailed information.

## Accessing the Deployments Module

Navigate to **DEX > Deployments** from the left-hand pane.

The Deployments tab displays a list of all active, scheduled, and completed deployments.

Click **Create Deployment** to begin a new rollout.

![navigation to workflow deployment](https://cdn.manageengine.com/sites/meweb/images/digital-employee-experience/help/dex/deploy-workflows1.webp)

## Creating a Workflow Deployment

### Step 1: Enter Deployment Details

| Field | Description |
|---|---|
| Deployment Name | Give the deployment a unique, descriptive title. |
| Description (optional) | Add context to explain the intent or scope of the rollout. |

![workflow deployment](https://cdn.manageengine.com/sites/meweb/images/digital-employee-experience/help/dex/deploy-workflows2.webp)

### Step 2: Define Resources

Set the **Type** to *Workflow*. Select one or more workflows from the list. You may also combine them with sensors if you would like to custom data along with workflow execution. Additionally, you can add multiple workflows or sensors as needed.

![Adding resources](https://cdn.manageengine.com/sites/meweb/images/digital-employee-experience/help/dex/deploy-workflows3.webp)

### Step 3: Select Target Devices

Choose one or more Custom Groups to define the scope. Narrow down target device using include / exclude option in target selection.

**Tip:** Test the deployment on a small group first before expanding to a wider audience.

### Step 4: Choose Deployment Mode

| Mode | Description |
|---|---|
| Immediate | Executes the workflow as soon as possible. |
| Schedule | Define a specific date and time for deployment. |

![Choose the deployment mode](https://cdn.manageengine.com/sites/meweb/images/digital-employee-experience/help/dex/deploy-workflows4.webp)

When schedule is chosen, you can select frequency such as Once, Daily, Weekly based on your needs. Define active period of the scheduled deployment and provide Run Time to trigger initial deployment.

### Step 5: Deploy

Click **Deploy** to trigger or schedule the execution.

## Monitoring Deployment Status

After deployment, return to the Deployments tab to monitor outcomes.

| Column | Description |
|---|---|
| Deployment Name | Click to view detailed device-level results. |
| Created By / At | Tracks creator and timestamp. |
| Status | Indicates progress: In Progress, Success, Failed, or Suspended. |
| Remarks | Shows summary messages or error notes. |
| Action Menu | Options to suspend, resume, edit, or delete the deployment. |

## Example Deployment Scenario

**Objective:** Restart reboot pending devices in the Sales department to apply pending security patches.

**Workflow:** “Restart Devices After Uptime > 30 Days”

**Sensor:** Uptime Monitor

**Target Group:** Sales_Laptops

**Schedule:** Off-hours (2:00 AM next day)

**Result:** 47 devices restarted successfully; 3 offline devices retried next sync cycle.

## Best Practices

| Practice | Why It Helps |
|---|---|
| Use meaningful deployment names | Improves traceability and audit clarity |
| Always test deployments in small groups | Reduces risk and ensures logic accuracy |
| Use scheduling for off-hours or change windows | Minimizes end-user disruption |