You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discord introduced a rate limit on requesting all guild members [(source)](<https://discord.com/developers/docs/change-log#introducing-rate-limit-when-requesting-all-guild-members>)
5
-
-# Despite the announced 01/10/2025 rollout date, it only took effect recently.
6
-
7
-
- Apps may only request all members **once** per **30s** per guild.
4
+
Discord introduced a rate limit on requesting all guild members (**once** per **30s** per guild).
8
5
- You will have to update your code accordingly to make sure this doesn't affect your app.
9
6
- Look for instances of [`guild.members.fetch()`](<https://discord.js.org/docs/packages/discord.js/stable/GuildMemberManager:Class#fetch>) with no user ids.
10
-
-# We are working on making the `GuildMemberManager#fetch()` call reject if we receive this rate limit after requesting members. This will likely land in the next release.
7
+
- Starting in version 14.25.0, discord.js rejects the returned Promise and exposes details in `error.data`.
11
8
-# If you confirmed this cannot be the reason, you can find other caveats [in our guide](<https://discordjs.guide/legacy/popular-topics/errors#members-didnt-arrive-in-time>) <:djsguide:862626783890636830>.
12
9
"""
13
10
reply = true
14
11
mention = true
12
+
13
+
14
+
[gw-ratelimit]
15
+
keyphrases = ["opcode 8 was rate limited", "gatewayratelimitederror"]
16
+
content = """
17
+
Discord introduced a rate limit on requesting all guild members (**once** per **30s** per guild).
18
+
- Starting in version 14.25.0, discord.js rejects the request and exposes error details in `error.data` but does not re-try automatically.
0 commit comments