Bungie Answered
Continue Waiting Error
First time running into this with 15 minutes left on Outpost and two teams wiped..
Unfortunate because I was looting a body on Destroyed Wing entrance and the game just booted me out but my internet connection is fine and it seems like the servers are up on Bungie's side.
0
Comments
Hi there,
Thank you for reaching out. I'm sorry to hear you were stuck on the "Continue waiting?" screen during your run. If you haven't already, please view our Network Troubleshooting Guide just to rule out any potential networking issues and to hopefully prevent this from reoccurring. You can also track your platform's server status to see if there were any outages.
If you get a "Continue waiting?" screen again, please try waiting and give it a few minutes to load you back into your game. If the error persists, please refer to our Network Troubleshooting Guide linked above, as well as our Help article for Optimizing Connections.
It is unfortunate that this appears to have been a client-related issue- as found in a previous thread on this bug:
Given the fact that I restarted my wifi + the game multiple times.. I don't understand why the game refused to give me a Reconnect option. The Run was still in session and the game did not take me to the menu until my teammate ex-filled. Thanks to that, I was brought to the Eliminated screen and all of my loot gone.
The fact that Gear Refunds are not offered for this situation & that I intentionally clicked "Continue Waiting" with no Reconnect option for the ongoing Run is pretty ridiculous.
Had I clicked Return to Lobby or if my Wi-Fi was down, sure- I understand those consequences. Yet, I am punished and lose gear / value nonetheless.
Hopefully this gets fixed and Reconnect Screens take precedent over Continue Waiting screens if connections and networks truly are stable. And if that is impossible.. then perhaps refunding the Runner's gear when they deliberately chose "Waiting" is more than fair.
With regards to your request for items lost, please note the following from the Network Troubleshooting article:
Please sign in to leave a comment.