Thank you! Very clear and calm. I was stuck for far too long on this - I had the old version of Orchestrator stuck in my head. Looking forward to your other videos
Thank you so much for the kind words, very much appreciated. There should be more stuff coming within a few days so (shameless plug) don't forget to subscribe 😜
I usually don't leave any comments on videos but this is the most straight forward video on setting up an unattended robot I could find. Also the clean up part was really helpful to consider in future. Thank you so much!
Hello Nico, and thank you very much for those comments. In fact, comments like yours make an enormous difference to my channel. First of all because it's nice for me to hear that you like it, but also because positive comments help my channel get more exposure on youtube, just like clicking the "Like" button and getting new subscribers. Very glad you liked it, and that you took the time to comment. 🙂🙏
My guess would be that the issue is License Allocation. In the Cloud Platform, select your tenant, click Licenses, then towards the top right click the "Edit Allocation" button and make sure you have at least 1 license allocated to that tenant. That may not be it, but it's my best guess....
When you click "Connect" in Assistant, it says "Connected to Orchestrator but was unable to retrieve a license. Please contact your automation department" yet the robot is still able to run a process from Orchestrator. Is that a known display bug? It looks as if Assistant is unable to acquire a license, yet it works anyway?
I was wondering if you could explain licensing for unattended processes? I though a single unattended license could be used across multiple machines so long as its one process at a time... but this doesn't seem to be the case!
Hi again :-) Bad news I'm afraid. An unattended robot license is bound to one machine, so no, you cannot run one job on Machine A and then another on Machine B with the same license. There is no way for robots ro release their license once a job has finished, and as long as the license isn't released, there is no way for another machine to acquire that license. I wish there was.
@@UiPathwithJeppe Hi again! 😀Thank you immensely for your help with this 🙏.It is really is too bad that they don't allow it to switch machines. I have a couple of ideas: 1 - one of my processes is relatively simple and background only, so I could code it in Python and use the AI document understanding API 2- The other process is very complex and has a lot of UI RPA interface. I could a) see if UiPath could reduce their license cost for this use case, b) Use a different RPA tool such as Blue Prism, which seems to have a more flexible license model.
@@TimothyHodgson-ds4oj it really depends on your setup. Could this work as an attended robot, perhaps? You might want to look into Automation Express license model, which is limited in some ways (Attended only), and essentially you have to build the automation on the machine where you want to run it. Also, it’s UiPath StudioX, but it is completely free to use. I made a video about it a loooong time ago: ruclips.net/video/K20sFggsTQs/видео.html
Thank you! Very clear and calm. I was stuck for far too long on this - I had the old version of Orchestrator stuck in my head. Looking forward to your other videos
Thank you so much for the kind words, very much appreciated. There should be more stuff coming within a few days so (shameless plug) don't forget to subscribe 😜
Your videos are always the best
I usually don't leave any comments on videos but this is the most straight forward video on setting up an unattended robot I could find. Also the clean up part was really helpful to consider in future. Thank you so much!
Hello Nico, and thank you very much for those comments. In fact, comments like yours make an enormous difference to my channel. First of all because it's nice for me to hear that you like it, but also because positive comments help my channel get more exposure on youtube, just like clicking the "Like" button and getting new subscribers. Very glad you liked it, and that you took the time to comment. 🙂🙏
Very clear and on-point way of explaining. Keep up the great work!
Thanks 🙏🙏😊
Another great video! I always enjoy your content.
Thanks a lot, I always enjoy your comments 😊👍🙏
Help! I'm always stuck in pending even after doing what you do to the letter... WHAT do I do?
My guess would be that the issue is License Allocation. In the Cloud Platform, select your tenant, click Licenses, then towards the top right click the "Edit Allocation" button and make sure you have at least 1 license allocated to that tenant. That may not be it, but it's my best guess....
When you click "Connect" in Assistant, it says "Connected to Orchestrator but was unable to retrieve a license. Please contact your automation department" yet the robot is still able to run a process from Orchestrator.
Is that a known display bug? It looks as if Assistant is unable to acquire a license, yet it works anyway?
Is this new version of orchestrator 2023??
And
how to connect attended robot??
I was wondering if you could explain licensing for unattended processes? I though a single unattended license could be used across multiple machines so long as its one process at a time... but this doesn't seem to be the case!
Hi again :-)
Bad news I'm afraid. An unattended robot license is bound to one machine, so no, you cannot run one job on Machine A and then another on Machine B with the same license. There is no way for robots ro release their license once a job has finished, and as long as the license isn't released, there is no way for another machine to acquire that license. I wish there was.
@@UiPathwithJeppe Hi again! 😀Thank you immensely for your help with this 🙏.It is really is too bad that they don't allow it to switch machines. I have a couple of ideas:
1 - one of my processes is relatively simple and background only, so I could code it in Python and use the AI document understanding API
2- The other process is very complex and has a lot of UI RPA interface. I could a) see if UiPath could reduce their license cost for this use case, b) Use a different RPA tool such as Blue Prism, which seems to have a more flexible license model.
@@TimothyHodgson-ds4oj it really depends on your setup.
Could this work as an attended robot, perhaps? You might want to look into Automation Express license model, which is limited in some ways (Attended only), and essentially you have to build the automation on the machine where you want to run it. Also, it’s UiPath StudioX, but it is completely free to use. I made a video about it a loooong time ago:
ruclips.net/video/K20sFggsTQs/видео.html
@@UiPathwithJeppe Hi Jeppe. Thank you again! I think that will work perfectly for one of the processes.
Great and useful video! I find that, UiPath's content on Orchestrator, is not as good as content on other features of the platform.
Well…. I do agree to a point, but to be fair, Orchestrator has gone through a lot of changes in the last couple of years.
Hi is it normal that the status colour is orange in Assistant?
you can sign in or enable trouble shooting session on monitoring tab then it will turn green