Vaal temple: instance crash (kicked to char select) counted as temple failure, and bugged creation

I had just started a temple run with key-chamber and atziri both connected, then when entering a room (I think it was a syntflesh sanctum, but not 100%), I got kicked out of the game and back to character select.

When I entered the game again, I was in vaal ruins, and looking at the temple device showed 2-3 rooms destabilizing, as if I'd finished a run. (considering I never left GGG's servers, identifying it as a server side "oops, our bad" instead of the player crashing or alt+f4 should be easy, so as long as the player returns before timeout, I see no reason to mark it as failed).

The 2nd and worse bug came when I then tried to do a new temple, I placed 6 rooms (and sacrificed a road-segment even though sacrificial chamber was maxed), then clicked "run temple", nothing happened except a message in chat:
Failed to open incursion Temple:Temple has already been opened. Please use Instance Management to create a new instance of the Vaal Ruins and try again.
Failed to open Incursion Temple.


My suspicion is that this 2nd temple will be counted as a failure too, due to timeout, and loosing me even more rooms (though maybe I'll be lucky and that won't happen).
My suspicion was wrong, the time it took me to write this post made the old temple time out it seems, and let me enter this new one (the message was a bit messed up though, since in the situation I was in, I couldn't make a new temple, unless you can controll-click the temple-control device?)

Either way, serverside problems shouldn't punish players (the way you've handled other types of serverside crashes with freezing us for a few seconds and giving us a new instance is brilliant)

Hmm, if I can even do this temple, there's high priests under the floor that can't be hit, but prevent the doors from opening to let me out of the room without using a portal to get out (it's the room connecting to atziri's access chamber, so I kinda want to do it though)