Automation Developer License Issue (Automation Cloud)

Help Studio
, , , , ,
1

Dear All,

I need insight, I found something abnormal about using an Automation Developer License from Automation Cloud

the case is you have 3 x Laptops L1, L2, L3 that have installed Studio v23.4.4 and you have only 1 x Automation Developer License assigned with User1.

my understanding is after User1 has signed in on L1. the same user will not be able to sign in again on L2 or L3. but I found that I can sign in with the same User1 on L2 and L3.

my understanding is proven if the Studio connected with OC on-prem.

so I guess there is a defect on Automation Cloud but I hope not. Please help me to correct my understanding.

thank you,
Cheers

2

Hi @irahmat ,
I think if you have multiuser license and u are connected to orchetrator it should allow u to use it with a condition that machine is defined in orch,robot is linked to the machine.
If you have linked 3 machines to the Orchestrator, then it will automatically “jump” between machines with a first come, first served principle
If all the 3 machines are available which means that consuming the license even when sitting idle then it will be consuming 3 licenses ideally.
hope it help,
LNV

3

Hi,

we don’t have multiuser licenses just named user. I guess we have the same understanding about first come first served but what I found was not like that. even if the first User1 has signed in, you still can sign in again with the same user with a different machine.

I remember this issue never happened on v22.10 but I don’t know why now it can do on the latest version.

Cheers,

4

I see, may be it’s update or error. I think we can login with a same user in multiple machine. But have you check when publish or set run unattended, could Oches can find machine?
regards,

5

my understanding is that a multiuser license is only able do sign in with multiple machines with the same user.
also, we can do publishing and other activities in the studio normally. and we cannot set run unattended (studio). also, we installed the studio with User mode instead of service mode.

Cheers,

6

I think with your license will similar, we can publishing but can not set run unattended, because Oches unknow, you can check it
regards,

7

thanks,

we know already automation developer license is not able to run unattendedly.

8

Hi,

I think Interactive SignIn is related to only user account and not machine. So,the above seems normal behavior.

https://docs.uipath.com/robot/standalone/2023.4/user-guide/setting-up-interactive-sign-in

Regards,

9

agreed. not related to the machines but again what I understand about interactive sign-in is first signed in first served.

no idea why first-signed in first served only works if your studio is connected with OC on-premise.

Cheers

10

Hi,

If I remember right, we can use any machine if use Interactive signin in my on-premise 21.10 environment.
Doesn’t your machine connect with OC via both interactive sign-in and machine key/Client ID?

Regards

11

Hi
do you mean a single username able to sign in on multi-machine simultaneously?

12

I think it’s technically possible. (but it may violate license term if use both at same time)
I’ll just check it out.

13

agreed. That might violate the license term however, this issue only occurs if your studio is connected with the Automation cloud.

because what will happen if your studio is connected with OC on-prems(Standalone).

the same user who signed in on another machine will have status connected but not licensed.

Cheers,

14

this issue still occur on the automation cloud 23.10.X