Dealing with too many environments

Getting straight to the point, remote chances are that you may be using way too much environments on a single release. Normally, this would never happen, as the usual route is to have dev, qa, staging, and production environments at most. And because of that, they never thought this could possibly become an issue.

When you edit a release, a web api call is made to check the current user’s permission to access each one of them. If this method happens to fail, you won’t be able to access the context menu options for each environment (such as variables or deployment conditions). Click here to read more.