I have an RPA Developer license and am trying to run my automations in our Prod Orchestrator environment. I was previously using a separate Attended User license to run these automations, but I was recently informed that this was not necessary, that I could use my developer license in Prod as well. However, I’m having difficulty setting this up. When I select “RPA Developer” as the Attended Robot license type, it gives me an error that there are no additional developer licenses available. That leaves me with the only other option that wouldn’t consume an additional Attended User license: “Inherit license from user’s group.” I checked to make sure the group I belong to has an RPA Developer license assigned to it and it does, however, I can’t connect in Assistant. Can I use my same machine key to connect to Orchestrator with the inherited license? It’s showing “connected, unlicensed.” What am I missing? What is the normal setup process for Citizen Developers & RPA Developers to be able to access their automations on Prod?
Hello, just checking to see if anyone has any insight into the license configuration to be able to use the Developer license on both Dev and Prod? It seems as though once it’s allocated in one environment, it can’t be allocated again. Is there a way to allocate a license to both environments?
To be crisp you cannot use the same license here
But for the group license part is it that another user in the group would have already consumed the license…so even that is not your way now
If you are having the developer license in prod itself then you dont need to assign an attended license because you already are a developer and you will have a studio and you can run from
That studio
Cheers
We prefer to keep our Dev & Prod environments separate & only use Prod to run published automations. What is the typical setup for this? Right now I am using my RPA Developer license in our Dev environment and a separate Attended license in our Prod environment to run the automations. I was told by UiPath that the Developer license can be used in both environments and I was hoping someone had a similar setup they could share before reaching back out to our UiPath sales team. Any help/insight is appreciated!
So to your point
Say machine A is your developer machine with user a then when you connect your assistant you have to provide the orch url and other details which are specific to the dev instance alone
So it is tied to your dev instance but no link to the prod.
So on prod to run it, an attended or separate dev license is needed as you have to run the bot in different instance
But even I am waiting to know if we can share and how. If you get an answer from someone or from uipath team please do share. Would be very happy as even we will try the same
Cheers
Thank you for your response/insight! I will let you know if I learn anything different.
Do you have access to the prod account? logging into the prod machine with the prod account credentials should allow you to troubleshoot processes using that account and that machine through studio. You may have to enable a troubleshooting session on orchestrator depending on your setup
Curious why you are bringing this super old thread up?
Regardless this is solved using the current licencing format where a developer licence is assigned on an organizational level, not a tenant based one, if it doesnt work that way it can be switched in the settings, all orgs will be migrated to this, with the legacy format deprecated shortly.
Hey @Jon_Smith
I was doing some research on licensing and ran across the thread and noticed it was unresolved and I figured I’d throw in my two cents in case anyone else ever ran across it.
My organization is still on stand-alone orchestrator (2022.10) and so the legacy licensing model is still relevant to us. I know the new licensing model is available on cloud (and I’m assuming suite). I don’t think it can come to a newer version of stand-alone on prem though, given that each instance is meant to be hosted on totally different servers, or can it?
And I also didn’t know they would shut off the legacy licensing model altogether on cloud either! The docs don’t mention it Overview - License management options (uipath.com) - do you know something secret? 
Its been in the documentation since October 2023
Looks like the timeline got pushed back though if my memory serves as I thought it was July 2024.
Nice thanks I didn’t know about that doc. But yeah, us stand-alone cavemen will have to continue struggling with the legacy licensing system for still some time to come. We’re transitioning to cloud more or less within that deprecation timeframe though, so it’ll be fun to redo all of that.
prashant1603765
ashokkarale
mively
anjasing
Yoichi
sonaliaggarwal47
lrtetala
V_Roboto_V
pikorpa
sharazkm32