How we use RM – Part 1

This post details issues encountered and fixes rolled out for the internal use of Release Management (RM) for VSTS deployments. It addresses un-actionable error messages by changing PowerShell scripts to log inner exceptions, improves traceability by introducing 'Release-level-approvals' to avoid unnecessary ring traversals, and discusses the need for agent upgrades to resolve large log file upload issues. It also outlines plans for per-scale unit environments to improve log clarity and introduces the 'Resume task on timeout' feature for manual interventions to replace 'sleep' tasks.