Skip to content

fix(guide): update 'Members didn't arrive in time' explanation #11277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −5
Open

fix(guide): update 'Members didn't arrive in time' explanation #11277

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions apps/guide/content/docs/legacy/popular-topics/errors.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,13 +187,19 @@ This error originates from an invalid call to `bulkDelete()`. Make sure you are

### Members didn't arrive in time.

This error happens when fetching multiple members via `GuildMemberManager#fetch()` and:
<Callout>
Discord recently implemented a rate limit to the `GuildMemberManager#fetch()` call of one fetch per 30 seconds per
server. You must update your code accordingly if you are receiving this error -- look for instances of
`guild.members.fetch()` with no user IDs.
</Callout>

This error is related to the `GuildMemberManager#fetch()` function. The error is emitted when you fetch multiple members and any of the following conditions are true:

- The `GuildMembers` intent is not specified or enabled in the dev dashboard
- The internet connection is somewhat bad
- The amount of members fetched is large (about 50 thousand and upwards)
- The one fetch per guild per 30 seconds rate limit set by Discord has been exceeded,
- The `GuildMembers` intent is not specified or enabled in the bot dashboard, or
- The internet connection is somewhat bad.

You can specify the time to wait for with the `time` option in the `.fetch()` call. Another solution could be to move your bot to a faster infrastructure, if available.
You can specify the time to wait for with the `time` option in the `.fetch()` call. If available, moving your bot to faster infrastructure may also resolve the problem.

### MaxListenersExceededWarning: Possible EventEmitter memory leak detected...

Expand Down