I also just had this happen to me, was walking around right next to a waypoint and then I got booted. I still can’t rejoin either.
Yes you do have to exit and restart the game, or should I say the queueing for blizz function.
Report it in game (when you get back in). Doing it here is nowhere near as effective.
Same, entered a dungeon with my buddies DC’d then I get this error code in the Character Screen before I log in.
Got disconnected then when I click Start Game I get “there was an error. (Code 316719) a few seconds. Keep getting this every time I click Sart Game. Relaunching the game let’s me queue up again.
Yes, it’s a beta.
But it’s SO unpolished, SO raw, and SO bugged, it should have gone through more and better internal QA before sharing this (or trying to, but failing) with the world.
just now too.
got disconnected. then this error…
too much for them…
Same error here… also if I create a new char…
disconnected mid-dungeon then error(316719) every time I try to launch the game on any character.
I easily spent more than 3 hours on queues today, this week-end has been much worse than the last one.
Just got the same error in the city transitioning out of part of the story. Clicking Start Game just gives the same error again, you have to close out completely and go back to queue.
I see disconnecting is still a big issue this weekend, as it was last weekend. Was hoping some of this would be better this weekend.
Twice so far. Both times had to exit completely and rehop into a 30+ minute queue… well, that made my decision that much easier… Not gonna purchase this junk. Thanks.
2 Likes
I can play 10 mins and waiting 1 hour !!
What a beta day 
This has happened to me now twice. This weekend so far is much worse than last weekend. I guess the extra logins and players are affecting the servers really severely.
Please fix this Blizzard. This is going to happen again in June when the game releases.
You have plenty of time to fix this so please do so. You are charging us more for this game than any other game release please don’t sit back with your fingers crossed and fix this for your player base.
“You are charging us more for this game than any other game release”
They need to since this beta is actively hurting their sales.
1 Like
I don’t think it is… I think a lot more people are hyped for it after having played it / seen it than they were before. So many people were hating it on just because it’s not D2 or because they think it’s just DI with p2w.
What evidence do you have that beta is hurting their sales?
1 Like
I keep getting disconnected and get stuck at the character selection screen with error code 316719. It only goes away if I exit the client and rejoin the login queue, but it means waiting 30+ minutes for 5 minutes of gameplay before it disconnects again. Not worth it.
1 Like
Same. Has happened at least 5 times.
1 Like
Well I’ve been on for the past 2 hours without issue now. This is after downgrading to the driver version I mentioned above. Hope that helps others.
Not sure how a graphics driver would help the “you’ve been disconnected from the server” messages… but good to know some people aren’t being booted constantly.
Tell me what you think… People are hyped to try it out, are met with 35+ minute queues and are repeatedly D/C’d to get back into 35+ minute queues… now, if they haven’t purchased the game yet, do you think that helps or hurts that player’s chances of buying the game.
I can assure you, the small section of gameplay isn’t that spectacular to begin with nor is it indicative of the end-game, but server stability is a thing that carries over… and before you say it’s not… I’d like to remind you about error 37 @ D3 launch that had plenty of players refunding their purchases.