Hi Luis,
This behavior of interleaved “now it works as expected” and “now it doesn’t” most often comes when there are 2 virtual services in “Running” mode on the VSE and they have been deployed with the same base-path and are listening on the same port.
In that case the VSE does a round-robin with the incoming requests and giving the request on turn to the first and then to the second.
If that is not the case, and it is only once deployed and shows this odd behavior, is this a customized .vsm? If so, what was customized?
Cheers,
Danny