KillProcess

The Kill Process activity is used to terminate a specified Windows process. It forcefully closes running instances of an application based on the provided process name or process object. This activity is commonly used to ensure that unwanted or previously running instances of an application interfere with the automation workflow.

Properties

INPUT

Process: Represents a Process object that identifies the specific process instance to be terminated. It is typically used when the process has been retrieved dynamically and needs to be referenced directly (for example, from a Start Process activity).

ProcessName: Specifies the name of the process to be terminated. It accepts a string variable representing the process name as seen in Task Manager (for example, “Notepad”).

Note: Either Process or ProcessName is mandatory.

MISC

DisplayName: Displays the name of the activity. The name can be customized for better readability and troubleshooting.

SkipOnError: Specify the “Boolean” value as “True” or “False.”

True: Continue executing the workflow regardless of any errors thrown.
False: Halt the workflow if it encounters any errors.
None: If the option is left blank, the activity will, by default, behave as if “False” were chosen.

Version: Displays the version of the activity being used. This field is auto-populated and read-only.

OUTPUT

Result: It provides the ability to view the execution status of the activity. It returns values in “Boolean.”

True: Indicates that the activity has been executed successfully without any errors.
False: Indicates that the activity has been unsuccessful due to an unexpected error being thrown.

Note:

1. In shared environments such as Citrix or VDI, forcefully terminating browser processes (e.g., Chrome or Edge) is not considered best practice. This can result in unclean shutdowns, causing browser sessions and extensions to reload or reinitialize. As a result, subsequent retries in the automation flow may experience additional latency and inconsistent behavior.
2. In shared environments such as Citrix, using the Kill Process activity with a process name may terminate all instances of the application across user sessions if not properly scoped. It is recommended to ensure session-level isolation or use alternative methods to safely close applications.