Skip to main content

Restart or stop the deployment of a package

Applies to: Medulla – Deployment
Version: All versions
Environment: On-Premise / Private SaaS / Shared SaaS
Category: Usage

From the deployment tracking views (Audit menu — “My tasks,” “My team’s tasks,” “My past tasks,” etc.), each deployment is displayed as a row. From this list, you can restart a deployment or stop a deployment that is still in progress or scheduled.

These two actions work for both deployments targeting a single computer and those targeting a group of computers. You just need to know how to read the relevant row.


Understand a deployment row

In the Target column of the list, the icon indicates the type of deployment:

  • A single computer: the target displays the computer’s name preceded by a computer icon. The Progress / Status column shows the status of that computer (for example, DEPLOYMENT START, SUCCESS, ERROR).
  • A group: The target displays the group’s name preceded by a group icon. The Total machines column indicates the number of computers involved, and progress is shown as a percentage (along with GROUP FULL SUCCESS, GROUP PARTIAL SUCCESS, or GROUP ERROR).

Any action you trigger on a row is therefore automatically applied to the correct scope: the single computer if the row targets a computer, or the entire group if the row targets a group.


Restart a package deployment

Restarting is used to rerun a deployment that has already been initiated—for example, after an error, if a computer was turned off at the scheduled time, or simply to redeploy the same package.

How to do it

  1. Locate the deployment row in the list.
  2. Click the Restart deployment action at the end of the row.
  3. A confirmation window opens. Its title specifies the scope:
    • for a computer: “Reload <package> on machine <computer name>”;
    • for a group: “Reload the deployment.”
  4. If desired, select the options below, then confirm.

The two restart options

  • Force re-deployment during initial validity period: forces the re-deployment even if the original deployment is still within its validity period. Check this box to re-deploy immediately without waiting.
  • Reschedule deployment between now and 1 day: Instead of restarting immediately, Medulla schedules the restart for a random time within the next 24 hours. This is useful to avoid overloading all computers at the same time.

On a single computer or a group

  • On a single computer: The restart applies only to this computer. The window displays its name to avoid confusion.
  • On a group: The restart applies to all computers in the group associated with this deployment.

After confirmation, the deployment is restarted, and you are redirected to My tasks, where you can monitor its execution (see Launch a deployment and monitor its execution).


Stop a package deployment

Stopping a deployment cancels a deployment that has not yet completed: a scheduled task (that has not yet been triggered) or a task currently in progress. A deployment that has already completed (listed under “Past tasks”) cannot be stopped: there is nothing left to interrupt—you can only restart it.

How to do it

  1. Go to My tasks: this view lists your ongoing deployments and, further down, your Planned tasks.
  2. Locate the row for the deployment you want to stop.
  3. Click the Delete deploy action at the end of the row.

Medulla will then delete the corresponding deployment command: the task will no longer trigger (if it was scheduled) and will no longer send new instructions to computers still waiting.

On a single computer or a group

  • On a single computer: only the deployment for that computer is canceled.
  • On a group: the deployment command for the entire group is canceled; computers in the group that have not yet received the package will no longer receive it.

Good to know: The cancellation affects only what has not yet taken place. A computer in the group on which the installation is already complete retains the result obtained; it is the remaining executions (scheduled or pending) that are interrupted.


Summary

  • Restart (Restart deployment): Available on each deployment row, including past tasks. Two options—force or reschedule within 24 hours.
  • Stop (Delete deploy): Available from My tasks for ongoing or scheduled deployments. Cancels the deployment command.
  • Computer or group: The action applies to the scope of the row—a single computer or all computers in the group.