How should a job started from Orchestrator be stopped?

Stopping a job that has been started from Orchestrator is specifically managed through the Orchestrator interface. This control is critical because Orchestrator serves as the centralized management platform for UiPath robots, allowing for monitoring, management, and maintaining the operational state of robotic processes.

When a job is initiated in Orchestrator, it is registered and tracked within this interface, providing visibility into its status and allowing for actions such as starting, pausing, or stopping jobs directly from the dashboard. This centralized management is essential for maintaining order and traceability over the processes being run in an enterprise environment.

While other methods, such as using the UiPath Assistant or command line, may allow for stopping processes that are running locally or independently, they do not directly apply to jobs initiated through Orchestrator. This ensures that the actions taken through the Orchestrator interface maintain integrity and consistency across the deployments and executions of automation workflows.