I was thinking about this error after a clan member had it happen, but was still able to sign back in. I was thinking, why is it that an error like this would be selective in who it hits. Is there something that the player was doing to bring about the error. On that thought, I remembered something I had trouble with going all the way back to D1. So, I am going to suggest something, but remember a few things first. 1. Sometimes the very simplest thing can fix the most stubborn problem. 2. I am suggesting this as I have not heard anybody mention it before. 3. I became an xbox ambassador because I enjoy trying to help people. I AM ONLY TRYING TO HELP HERE!!!! 4. Don't yell at me for a suggestion, because I am only trying to help you. Ok, from what I am hearing, most get the error at the character select screen. Now, since the days of D1, I have always had a problem there, if I did not sign out of Destiny before shutting off my console. I always got an error, though I never really paid attention to the name of that error. I found that if I signed out of Destiny, using the dashboard, that I had no problem signing back on. It seemed as though if I shut down my console without signing out of Destiny, that the game would attempt to bring me back to the instance I was playing when I shut the console down. I always got an error when it tried to do that. So, if you can get to the character select, instead of trying to choose a character, hit the xbox button, highlight Destiny 2, then choose quit. We had a clan member get the watercress error, and were worried that he would be in the same boat as many are now. He signed out, out of habit, and was able to get back into the game. Now, I have no idea if this will work for other people. I have no idea if other people have already tried this. I only want to try to help, looking at something simple, that appeared to work for a clan member, I pass it on to those on the forum having the problem. I truly hope that by some unbelievable chance, that it works for everybody having the error. Good luck if you decide to try it. It can do no harm if you try it or not, what do you have to loose? EDIT: What I am suggesting here is using the console dashboard to quit out of Destiny 2, NOT the in game settings. I remember once, as well, being in the preview program, that an early version of the new dashboard, made playing Destiny impossible. Maybe going to the dashboard to sign out, like my clan member did, does something different. I guess I confused some with my post, so here is exactly what I am suggesting you try. When in the game Destiny, or at least as far as you can get on the loading screens, hit the big button that lights up on the controler, it has a big x on it. Your menus will come up. Look for Destiny. Hit start while on the Destiny icon. Scroll all the way to the bottom, where it says Quit. Hit quit. That will completely log you out of Destiny. Then, try restarting the game. See what happens. Sorry for any confusion.

[b]BNGHelp6[/b] replied in other forum: [quote][i]First off, I completely understand everyone's frustration with the WATERCRESS and NEWT error codes. We are frustrated, too. My team is constantly seeing reports and engaging with players about the issue. I know our message is the same for everyone, but that is because we don't have any other information to provide. When we suggested Cross Save as an alternate method to play, it wasn't to suggest that players purchase anything, but that it's an option if they already have it set up. That's on us for sharing information without explaining that it's just a workaround and not a solution. Secondly, the teams investigating these issues don't work on live events like Guardian Games - that's an entirely separate team. We have many teams who work on fixing the game, too, which is why we had an update this week. While other teams are creating content or working on updates, other teams investigate and fix issues. Lastly, Bungie is taking these error codes very seriously. We know why WATERCRESS and NEWT occur but haven't found a solution to deal with them. We have teams dedicated to each one to try and figure out how to solve them. We don't want players to have these issues and we especially don't want them to not play. I can't begin to imagine the frustration you have about this and our lack of progress toward a fix, and I know this message probably won't help at all, but we are doing the best we can to resolve this as quickly as possible which is why we continue to talk about them, and other error codes, in our blog posts each week.[/i][/quote]

Seriously it's still not fixed? "Hey let's make the whole season depend on grinding and then lock out random players for a long time?" "Great idea!"

Here is something I wanted to share with you. Upon checking your account, we were unable to find an issue with your Xbox Live profile, there’s no corruption in the backend that could been preventing you from accessing Destiny 2. In this case, the problem has been isolated to your Bungee profile and for that matter, you’ll need to try contacting the support staff to see if there’s a way to restore your profile to a healthy state without deleting the progress associated with it on the Xbox platform. Thanks again for your patience, it’s highly appreciated and rest assured that if there’s something else we can try in order to help you, feel free to reach out

I got to character select and signed out relaunched and was able to play a little bit! Like 4 forges. At least its something.

-BNGHelp6- Please don't delete your character in an attempt to test out a fix for the Watercress error. We are actively looking into the issue but don't currently have a resolution yet. We know it's a result of having too many "player sessions" opened. This basically means that when you quit Destiny 2 your session for that time played should go away, but this doesn't happen for a small number of players on Xbox. Unfortunately, the only current resolution is to play your account on another platform with Cross Save.

What xbox are you on?

Try going to bungie.net and looking up watercress

I have a post running for affected players (see poll section on here) So far 261 players have logged how long they have not played. We know we can't log onto a character because it says we have a session already running however in the early stages we could play on a character for a limited time only. It would seem the problem lies between the "choose character and it loading" I am wondering are our character databases still ok or screwed up completely however as we could load them I'm presuming they are still safe. My idea is if we open a second account can Bungie set up a screen that initialises at the Watercress error point giving us the option to transfer our characters and inventory to the second account. Only players who receive the error code would be able to do this and not ordinary non affected players. This would bypass the original account that has the problem and we know that players who have such accounts on the same consul can play Destiny. There may well be problems doing this but I'm basing my idea on the DI to D2 transfer of inventory between the two versions.

Just keep checking the twab each week, they'll announce when it's fixed then try.

I'm sure you've likely been in the help forums for this but I believe at one point someone there was making a list of gamertags that were affected by this, from what I understand there's a bug that is only affecting some accounts, and it's causing the game to think you're still logged in when you quit out of destiny, even if you uninstall the game, so next time you're trying to log in it causes a crash, I'm sure this is an oversimplified description of the issue but the point is the list that was created was so bungie could manually force logouts on those accounts that were affected. This was about a month or so ago that I saw this so I apologise if it's outdated at this point.

Alas I am also a member of the Watercress Clan and cannot do any BOUNTIES AT ALL 😤

Bcuz of error codes. I can’t play destiny 2😭. I tried everything. I guess it will help me stop my addiction from playing destiny.

You lot are a small amount of Xbox players. Buy a PS4 or a PC, peasants. We have more important people to cater to. Now excuse me while I go wash up for my streamer orgy -Bungie

Try logging onto your account through Steam. My friend has the same issue, but for whatever reason can still play with his account through Steam. If you don’t have a PC that can run Destiny 2 maybe try Stadia as a last resort.

Im sorry but what is watercress? Im assuming its an error code?

Its not a problem ok your end, it is 100% Bungie. You can do all the troubleshooting and it makes no difference. I keep having the same problem, although half the time I manage to get on, but I cant do more than one trip without getting newt and then watercress. Yet my husband can sign in on my xbox and load no problems on the same internet, literally in the next room. Also I can quite easier play eso an actual mmo and be perfectly fine. I have done trials with 11 other people no problem and was in an area with 30 people crafting, again no problems. Keep at it! Maybe you will get lucky or Bungie will finally fix it. I also want my money back too if they don't 😊

It isn't your fault. Trouble shooting will not solve it. It is an issue on Bungie's end, and for the last five weeks a portion of the playerbase on XBOX has been unable to play the game. Even worse when you consider that many of these players have forked out cash for a season that they can no longer access...... but, you know, they had other priorities ... like the predictable dumpster fire that is Trials and their amazingly thought out "watchable" content..... but hey, who cares if people can't actually [i]play[/i] the game.... we can just go watch someone else! Talk about innovation!

If they had any ethics at all, ANY ethics at all, they would refund people getting error codes and give them credit for another season or DLC to make it right. Simply keeping the season pass payment and saying "we're looking into it" in the TWAB is horrible.