Release : SAAS
Component : BLOCKMASTER
We investigated this issue and the root cause seems to be owing to a short network outage where the <<COMPANY>> proxy server was not able to connect to Blazemeter. This resulted in the agent and the VSE being considered inaccessible and hence the Mock Services were updated with that status message. We are working on a solution where we can add self healing / recovery capability to Mock services so that they can recover and turn back to Running once the agent is back on the network.