Skip to main content

Stop Process Action

Terminate a running process on a device as part of an automation pipeline.

Updated this week

Introduction

Terminate a named process on a managed device during an automation run. Useful for stopping applications before updates, clearing stuck processes, or enforcing software policies.


Stop Process Action

From the automation pipeline in edit mode, click + and select Stop process from the System category.

Action Picker - Stop Process

The action panel opens with a single configuration field.

Stop Process Action

Process name

The name of the process to stop. Required.

Enter the process name as it appears in the process list β€” typically the executable name with the .exe extension, though Level may accept either form.

Example: notepad.exe, chrome.exe, myapp.exe

πŸ’‘ TIP: To find the exact process name, navigate to Manage β†’ Processes in the device details for a target device. The process list shows a column "Process Name" which is exactly what this action expects.

Click (x) to insert a variable, system variable, or custom field reference. The value resolves at runtime before the action executes.

⚠️ WARNING: Stop Process terminates the process immediately without prompting the user to save. Use with caution on any process that may have unsaved user data.


Conditions

The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action.

See Action Conditions for the full reference on condition types, operators, and values.


Additional Options

Expand Additional options for action name, failure behavior, output variable assignment, retries, and the enabled toggle.

See Actions Overview for the full reference on additional options available on every action.


FAQ

  • What if the process isn't running when this action executes? The action will likely fail or report that the process wasn't found. Use an Action Condition with Action status = Failed and Suppress and continue in Additional options if you want the pipeline to proceed regardless.

  • Does this stop all instances of the process? Needs confirmation β€” if multiple instances of the named process are running, it's unclear whether all are stopped or just one.

  • Who can add or modify Stop Process actions? Technicians with permission to edit automations in the relevant group. See Workspace β†’ Permissions for access control configuration.

Did this answer your question?