RobilityAI®

Header Example

Robility® Forum

Unleash your potential – connect, collaborate, and automate with our powerful solutions.

Machine configurati...
 
Notifications
Clear all

Machine configuration on project

6 Posts
2 Users
0 Reactions
598 Views
Posts: 0
Guest
(@Anonymous)
New Member
Joined: 1 second ago

Why do we need to remove and unassign a machine from one project to add the same machine in another project within the tenant?

Reply
5 Replies
Posts: 73
Robility Support Team
(@abidurai)
Member
Joined: 1 year ago

@abi-nandhan

Hello, since the licenses are allocated based on the project, Unassigning a machine ensures that licenses are properly released from one project and reassigned to another without overusing resources.

Reply
Posts: 0
Guest
(@Anonymous)
New Member
Joined: 1 second ago

@abidurai I am not going to use the same machine when it is connected to one project or when it is in running state. I need to connect the same machine when it is IDLE. Each time I need to remove and unassign to connect to another project.

Reply
Posts: 73
Robility Support Team
(@abidurai)
Member
Joined: 1 year ago

@abi-nandhan Understood, Even if the machine is idle, it’s still considered assigned to a project. By unassigning the machines, the platform ensures that machines are cleanly isolated between projects, reducing the chance of residual settings or conflicts impacting other projects. The license key is provided based on the project level, same machine can be used multiple times within the project, but you have to remove and unassign to connect to another project. That’s why the licenses are not provided at tenant level.

Reply
Posts: 0
Guest
(@Anonymous)
New Member
Joined: 1 second ago

@abidurai But still, it requires additional resource to do this job. Is there any alternatives?

Reply
Page 1 / 2