Try using /public the first time you use the new port. Then close the RR process, and then run it as /local.
What happened for me is that I used the new port but the first time I ran it, I also used the /local switch. This does seem to work but it doesn't list the Resource in Control Room, even though an entry will be created in the Resource Management section in the System tab. So, I started like this first:
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\Automate.exe" /resourcepc /port 8180 /sso /public /dbconname db_connection_name_here
Then after it added the Runtime Resource entry into Control Room with the port number appended to the name like 'MachineName:8180', I exited the RR process. And then I ran it like this:
"C:\Program Files\Blue Prism Limited\Blue Prism Automate\Automate.exe" /resourcepc /port 8180 /sso /local /dbconname db_connection_name_here
And it shows up for me in Control Room now as a local resource, assuming I'm logged into the same machine.------------------------------
Dave Morris
3Ci @ Southern Company
Atlanta, GA
------------------------------
Dave Morris
3Ci at Southern Company
Atlanta, GA