Discord API seems to have issues with Sharded bots

[Andre601]

There seems to be some sort of issues recently, where sharded bots are unable to load properly, when attempting to cache/chunk information like members and similar.

This issue only seems to affect bots with multiple shards as single-sharded bots are unaffected. The issue could be caused by large amounts of events being fired during the chunking which could be caused by Discords with large member numbers (e.g. Bot lists). It is so far confirmed by me and another dev which has a sharded bot and the only real solution is to disable the Chunking/caching, which is sub-optimal as it restricts us in special cases.

Did the API receive a recent change which may affect sharded bots that way? (Also, sorry to ask this here, but I don't think this is in any way caused by the library I use)

[night]

Can you provide specifics of the behavior you are seeing? Example payloads being sent as well as responses from the server vs what you expected. And then also include the payload you are sending for IDENTIFY. If this data contains PII/credentials then please redact any PII/credentials before posting.

[Andre601]

I'm honestly not quite sure how I could find out what payload is actually send on startup... I generally just wanted to know if the API might have received a minor change which now could affect the bots.

If it helps at all: I use the JDA library for running the bot and I don't use any audio-related things.

[GamingGeek]

I am also having issues with chunk information and my bot not loading correctly. My bot sends the IDENTIFY payload but never receives a ready event. I am using discord.py and have not sharded my bot.

The IDENTIFY payload is

{
   "op":2,
   "d":{
      "token":"super secret token",
      "properties":{
         "$os":"linux",
         "$browser":"discord.py",
         "$device":"discord.py",
         "$referrer":"",
         "$referring_domain":""
      },
      "compress":true,
      "large_threshold":250,
      "guild_subscriptions":true,
      "v":3
   }
}

[night]

The issues with requesting guild members should be fixed now.

[freyacodes]

The issue does not appear to be fixed. Are you still rolling the update out?

[night]

@Frederikam we should have hotpatched the existing code. do you have a guild id i can query?

[freyacodes]

None of my shards are starting. I do not have transparency into what exactly is happening over the websocket.

Edit: Nor any particular guild IDs.

[Xevryll]

I am also having issues with Gnar connecting to Discord. Oddly enough only a select few shards seem to want to connect https://i-got-scammed-by.gnarbot.xyz/2cHUpft.png

[advaith1]

543225764036870167 has been having connection issues for over an hour, and Dyno has been down too

[night]

This should be actually hotpatched now.

[AlekEagle]

bots 605864767915294730 and 503720029456695306 are both not working, they are both sharded and we are having issues, they refuse to connect to the 0th shard

[Xevryll]

My bots issue seems to be fixed now @night