Open MickBadran opened 6 years ago
There is some allocation logic in the service today that can put you on different deployment clusters / paths and might explain why this happened, but without specific resource-ids, region info and time it's hard to tell exactly what hit you :-)
We are however continuously updating the service @mattrowmsft
I had a previously working solution up for a few days and then it failed.
I then redeployed from VSNET which timedout and failed after 2.5hrs (which I tried 5 times - clean build, redeploy etc)
I then deleted all my SF artifacts and then redeployed and it worked!!!
Yay!!!
Q. Was there an environment upgrade? (if so - where could I find this information so I could just go straight to delete and redeploy stage)
Have a good one,
Mick.