Symptoms

Workflow Deploys but after +- 15 minutes error is thrown, looks like a timeout al though the deployment in the back ground succeeded
 

Diagnoses

We can confirm that the exception is caused due to Azure connections timing out after 4 minutes and we can't change that.
We have logged a bug and will be making one of the following two solutions.
1. We want to implement more efficient error handling to explain to the client the Azure connection timed out, but the Workflow could still have deployed successfully (Which is confirmed it does).
2. The preferred solution would be to limit the time we have connections open between browser and IIS Service by making multiple calls to see if the deployment is still busy or not.
 

Resolution

bugs have been logged to implement one of the changes mentioned in the diagnosis, for the time being even if the timeout occurs the deployment is already send to the K2 Server and will complete.