End process

What the End process action does, which settings it has, and when the step fails.

End process ends every running process with a given name on the device, for example a hung application. The device must be online.

Configuration fields

Field	Type	Required	Default	Description
Process name	text	Yes	—	Exact name of the process, for example `notepad` or `notepad.exe`. Case does not matter, and a trailing `.exe` is optional. Partial names and wildcards do not work. Supports variables `${{ … }}`.

Platform support

Platform	Supported
Windows	Yes
Linux	Yes
macOS	Yes

Outputs

Output	Description
`matchedCount`	Matched processes: how many running processes matched the name
`killedCount`	Ended processes: how many of them were ended or had already exited

Result behaviour

Case	Result
All matching processes were ended	Succeeded
No matching process was running	Succeeded, `matchedCount` and `killedCount` are `0`
At least one matching process could not be ended, for example because access was denied or the device did not confirm in time	Failed. The step details list the affected processes. The step still tries to end the others.
The process name is empty after variables are resolved	Failed
The device is offline when the step starts	Device offline. Depending on If device is offline, the run ends with this status or the step is skipped.
The device does not return the process list in time	Timed out, the outcome is unknown

You can safely repeat the step: once the processes are gone, another run simply succeeds. Each matching process is ended together with its child processes.

If a very large number of processes with similar names are running (more than 100), the step can miss some. In that case, just run it again.

Ending a process discards its unsaved data without asking the user first. Test the step on a single device first.

Was this helpful?

Still need help? Ask the team