Pull Members
Results and Troubleshooting
What each member result in a RestoreCord pull means, every error you can get when starting one, why a migration fails, and how to fix each problem.
Every member in a pull ends with one result, and every problem has a cause you can check. Find the counter, message or symptom below and follow the fix.
Member Results
| Result | Counted as | What happened | What to do |
|---|---|---|---|
| Pulled | Members Pulled | Discord added the member. | Nothing. |
| Already in the server | Members in Server | They were already a member. | Nothing. They don't count towards the pull amount. |
| Authorization refused | Members Unauthorized | Discord refused to refresh their authorization, or no longer knows the account. They're marked as no longer authorized. | They have to verify again. |
| Too many servers | Members in Maximum Servers | Discord won't let them join another server. | They have to leave a server first. |
| Banned | Members Banned | They're banned from the destination server. | Unban them in Discord if you want them back. |
| Account needs verifying | failed | Discord requires them to verify their account first. They're marked as no longer authorized. | They have to verify their Discord account, then verify again. |
| No usable token | failed | Their saved authorization is missing or empty. They're marked as no longer authorized. | They have to verify again. |
| Missing permissions | failed | The bot isn't allowed to add members. 15 in a row fail the migration. | Give the bot's role Create Instant Invite. |
| Bot not in server | failed | The bot was removed from the destination during the pull. | Invite the bot back and start a new migration. |
| Other errors | failed | Discord rejected the request for another reason, or kept failing after 5 tries. | Check the bot's permissions and try again later. |
Discord rate limits, timeouts and outages are never a final result. Those members are retried automatically.
Errors When Starting a Pull
These appear as a message in the dashboard, or as the message of an API error. Nothing is started.
| Message | Cause | Fix |
|---|---|---|
| Invalid bot token. / Unable to validate bot token. | The bot token was reset or Discord couldn't be reached. | Update the token in Bot Management, or try again. |
| Bot not found. | No bot is linked to the server. | Link a bot to the server. |
| No members found for migration. | No eligible members after filters. | Loosen filters, or check members still authorize the bot. |
| Bot does not have access to the target server… | The bot can't see the destination server. | Invite the bot to that server. |
| Target server not found. Ensure the bot is a member of the server. | The destination doesn't exist or the bot isn't in it. | Invite the bot, or pick another server. |
| This server has invites disabled… | The destination has invites turned off. | Re-enable invites in Discord Server Settings. |
| Bot doesn't have permissions to assign the selected role… | The role is above the bot's role. | Drag the bot's role above it in Server Settings › Roles. |
| The selected role does not exist in the target server… | The role belongs to another server. | Pick a role from the destination server. |
| Invalid role ID. | A role ID isn't a valid Discord ID. | Use the role's ID from Discord. |
| Discord is temporarily rate limiting the target-member check. Try again shortly. | Discord is limiting the bot. | Wait a few seconds and try again. |
| Unable to read members in the target server… / Unable to verify guild invite status… | Discord returned an unexpected error. | Try again later. |
| A migration start is already in progress for this server. | Another start for this server is still being processed. | Wait up to a minute and check the Migrations page. |
| Too many requests. Please try again later. | More than 5 starts in a minute. | Wait a minute. |
| Invalid target Discord guild ID format. / Invalid input… | A field is missing or out of range. | Check the settings and ranges. |
| You don't have permission to perform this action. | You're a sub-user without Pull Members. | Ask the owner for the permission. |
| An unexpected error occurred | Member analytics for a filter were unavailable, or another server error. | Try again in a moment, or without Smart Filters. |
| Something went wrong, contact support. | The migration couldn't be created. | Try again, then contact support. |
In the popup, Invalid Bot Token means the bot token was revoked. Click Manage Bots to update it.
Why a Migration Failed
| Cause | What to check |
|---|---|
| Invalid bot token | The token was reset in the Discord Developer Portal. Update it in RestoreCord. |
| Invalid client secret | The bot's client secret was reset. Update it in Bot Settings. |
| Discord blocked invites | Discord isn't letting new members join the destination server. Check its invite and safety settings, then try again later. |
| Missing permissions (red warning) | Give the bot's role Create Instant Invite, or re-invite the bot. |
| Destination couldn't be prepared | The bot couldn't change the notification setting or read the member list. Check that it's still in the server. |
| Repeated crashes | Rare. Start a new migration. If it happens again, contact support. |
Members pulled before the failure stay in the server. Start a new migration to carry on; members already there are skipped.