The problem is not about the unattended workflow.
As when I tried to upload the same packages to my cloud orchestrator, it shows that the process is unattended in the processes there.
And
- The workflow can run in unattended robot as when I manually start using the unattended robot while the virtual machine is signed off is successful to run.
- In the Orchestrator Cloud, I am able to create trigger, However, I am not able to create trigger on the local Orchestrator.
- The trigger setting there is correct as I am able to create trigger for other process
- The create trigger of specific workflow’s specific robot area did appear after I create trigger for the other process, cancel it, and recreate trigger for the specific workflow.
PS: The local orchestrator is my own orchestrator, not the company one. And also created a bug post as I feel like this is more like a bug.
The post is Orchestrator create trigger sometimes ok sometimes not - Feedback / Orchestrator - UiPath Community Forum
Thank you.