I have been trying to find the final answer for this question for a few days…
What is the final answer?
Is using UiRobot.exe with Windows Task Scheduler working till now? cuz when I tried no matter what i do (Running .nupkg with .bat, runing .xaml with double quotes) it does not seem to work and the task ends with 0xFFFFFFFF.
Is Orchestrator a must to schedule an unattended task? Is it necessary to purchase a license to use it for production?
Ensure proper permissions: Make sure the user account running the scheduled task has the necessary permissions to access the required resources, such as files and folders.
Working directory: When running a UiPath process through UiRobot.exe, the working directory might be different from what you expect. Ensure that the working directory is correctly set in the Task Scheduler or adjust the process to use absolute file paths.
Environment variables: UiPath processes may rely on specific environment variables. Ensure that the Task Scheduler environment is correctly set up to include the necessary variables.
Log files: Check the log files generated by the UiPath process to see if there are any error messages or indications of what might be going wrong.
Debugging: Try running the UiPath process manually outside of the Task Scheduler to see if it works as expected. This can help identify if the issue is related to the process itself or the Task Scheduler configuration.
Double-check command line parameters: If you’re using a batch file to call UiRobot.exe, ensure that the command-line parameters are correctly formatted. Make sure the .nupkg or .xaml file paths are enclosed in double quotes if they contain spaces or special characters.
Update UiPath: Ensure you are using the latest version of UiPath and that there are no known issues related to Task Scheduler compatibility in the version you are using.
UiPath Orchestrator: If your process relies on Orchestrator assets or configurations, verify that the Orchestrator connection is properly configured.
The error code 0xFFFFFFFF typically indicates that the process was terminated by another process, which could be caused by an issue with the process itself, or it could be related to how the Task Scheduler is interacting with UiRobot.exe.
=> If you are using community edition, no need to buy the license. Default for this version you have one attended and one unattended robot.
=> You can trigger your process in the Orchestrator.
To trigger the process in Orchestrator. You have to publish the workflow as a package. Then you have to create a process with that package. You have a trigger tab in the Orchestrator. To trigger the bot in specified time.
But there is a setup to make unattended robot in the Orchestrator.
Since you are using the community edition you can take the advantage of the one attended bot you get by default https://platform.uipath.com/
You can also manunally trigger from the UiPath Tray, you have the option to set reminder in UiPath tray if it is a time critical process.