As you play through Destiny 2, you’ll be met with several different error codes from time to time that have various fixes. There’s no need to be concerned, as many of them have very simple resolutions that take little to no time at all to correct. For instance, many of the errors simply require a restart or a reconnection to the servers to restore functionality. One such error you may run into is error code Chicken, which can be a frustrating one to have to deal with, but it’s easy to get by.
This error, which has been showing up since the original Destiny, can be resolved by retrying the very activity you were doing before the error occurred. Bungie’s suggestion after that is to exit Destiny 2 and then relaunch the game. Make sure you’re doing a full exit of the game when you go to do so, because simply going out of the game to the menu and resuming isn’t going to help much, since you’re just suspending the game.
If the error keeps happening, there’s the potential that it may be due to testing that’s been going on with Bungie’s end. The official advisory is to watch help.bungie.net and then follow the Twitter account @BungieHelp for any pertinent updates that might shed some light on your situation in Destiny 2. You should be able to follow up with any issues you’re continuing to have from there.