I am receiving what seems like a healthy API endpoint response whose body is: “Failed to get runspace” for many calls to my endpoints. It seems load-based, I guess.
Configuring the PowerShell environment to use more maximum runspaces seems to make it worse. There is no resource contention on the server.
How can an API developer get visibility into this issue? How can we track runspace usage, react to this strange “healthy” response, and determine which resource is in demand?
Product: PowerShell Universal
Version: 4.1.8