This post is based on personal experience with the error codes after seeing them plenty of times. In no way am I an expert on connection issues, so I don't know exactly what causes each individual error. Error codes looked at in this post are: Currant, Cabbage, Lettuce, Quail and Rabbit. Some of you may not like to hear this, but these error codes appear to happen if you have an unstable connection with either Destiny 2's servers OR someone else in an instance (or activity session). I can tell you right now that my internet provider hasn't been doing the best for the past month and these error codes started popping up for me pretty frequently, Cabbage in particular. So yeah, it's probably an internet provider problem on your end if you see these errors. Now when do these particular errors tend to happen? Let's look at each one. - Currant. This error code likes to pop up before you start loading into an activity. If you're in Orbit, you won't even make it to the traveling screen (warping to another destination or flying down to your current one). You'll just instantly black-screen and appear back in Orbit again. - Cabbage. This one occurs after a loading screen or if you are flying into a destination. If you are already at your destination and you pass through a load zone into a different area, you might notice there are missing entities in the area (enemies, chests, patrol beacons, mission objects, etc.). You may still be able to move around, but after about 30 seconds, you will black-screen and be booted to Orbit. While you are flying in from Orbit, even though you can't see it yet, the area you are traveling to does load to a point that can let this error trigger as well. This error can even occur if you are the only Guardian in an area. - Lettuce. This one usually occurs while you are flying into a destination. Sometimes, this error might happen in place of Cabbage, but it's usually more instant. However, if you see this error code, there is a possibility that you will not be able to rejoin that particular activity session, as you may receive this error again, or you will probably receive error codes Rabbit or Quail. - Quail. This error, from what I've seen, seems to mainly happen after you try to rejoin a session you've already been booted from by another error. This one happens while you are flying into the destination. If you see this error, you will probably keep seeing it as long as you continue to try rejoining the session. If you were in a fireteam, they must leave that session before you can rejoin them. This is the rarest of the 5 error codes discussed in this post and this is still based off of my experience, so take this one as you will. - Rabbit. This one tends to happen if you are flying into a session with other players, like Crucible. Instead of just spontaneously black-screening while you are flying in, it usually fades to black instead, like the session ended itself smoothly, except just for you. This error also tends to happen if you try to rejoin the same session. Sometimes, your Guardian might successfully load in, but everything else will not load properly and you will be kicked to Orbit by Rabbit or a different error code. Now, obviously, if you can improve your internet connection somehow, either by changing your setup or contacting your provider, you can reduce the amount of errors you see. But some of you might be wondering if there's anything in-game you can do to prevent any of these errors. There is one error from this list you can potentially escape from in-game. - Cabbage. You can potentially avoid this error as long as you are already loaded in as your Guardian at your destination. If you notice any entities are not loading in or there's something weird going on with other Guardians, see if you can find another loading zone. If you are fast enough and you go far enough past the load zone, you can go back to where you were and everything might load correctly. If done successfully, this error will not happen. Of course, this only works if you can get to another load zone. Everyone's experiences vary. These errors are described here as they've happened in my experience. But hopefully this at least helps some of you understand how these error codes work a little.