- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Troubleshooting
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET6 Projects Fail to Run
Disable Stop Button
With the higher demand of improving the relationship between humans and UiPath's Robots, we have developed a new feature that allows you to have processes that run continuously.
This is called "Disable Stop Button" and keeps them running at all times making it easier to deploy processes to users and keeping them running without the need of user interaction.
These type of processes can work hand in hand with triggers to initiate a workflow, the trigger can be a new mail, incoming phone call or other specific action defined in the project.
To create a process that can't be stopped from the UiPath Assistant, you have to go to the Process settings in Orchestrator and select "Process can’t be stopped from UiPath Assistant".
- If you choose to only enable the "Process can’t be stopped from UiPath Assistant", the process has to be started manually from Assistant.
- If you also enable "Automatically Start Process", when Assistant is first started on the user's machine, the process starts as well.
UiPath.Executor.exe.
