I think there is a bug in 5.0.10, maybe earlier version as well.
After I made a discovery of installed powershell 7, I created a test API which pointed to the pwsh env, which called “Powershell Installed”, then I renamed the env to “Powershell 7 Installed”.
I suspected the API hardcoded to the name, not some id.

Product: PowerShell Universal Version: 5.0.10
798ac7b9002fd229f0eca73d99ff3611c49396b4.png
d0b7a7ec8207b5dac2ec5331cbb0cdf49987fd89.png
This is a bug. I opened an issue for it. Renaming an environment does not rename it resources that use the evironment · Issue #3897 · ironmansoftware/powershell-universal · GitHub
Adam Driscoll
PowerShell Expert and Developer at Devolutions