> Your RestoreCord pull finished with fewer members than expected? What each outcome means, which members can't be added by any tool, and how to close the gap.

Source: https://restorecord.wtf/pull-came-up-short

# Why didn't all my members come back after a pull?

Your pull finished, but the member count is lower than you hoped. That's normal. Here's how to tell whether the gap is expected and what you can still do about it.

[Open the dashboard](https://restorecord.com/login)[View pricing](https://restorecord.com/pricing)

Short answer

RestoreCord can only pull members who verified before the incident and still have valid authorization. The rest show an outcome in your migration history: unauthorized, already in server, banned or blocked, a bot permission issue, Discord limits or filtered out. Fix what you can and invite the rest to verify.

## The big one: only verified members can be pulled

This explains most gaps. RestoreCord can add someone to a server only if they **verified before the incident** and granted your bot permission to join servers for them. Anyone who never verified isn't in your member list at all, and no tool anywhere can add them for you. If half your old server never verified, a pull bringing back about half is exactly what you'd expect.

## Then, member by member

Open **Dashboard → Migrations** and look at the pull you ran. Each member who wasn't added has a reason:

| Outcome              | What it means                                                             | What you can do                   |
| -------------------- | ------------------------------------------------------------------------- | --------------------------------- |
| Unauthorized         | They removed your app, or their access can no longer be refreshed         | Ask them to verify again          |
| Already in server    | They were there before the pull reached them                              | Nothing. That's good news         |
| Banned or blocked    | The destination bans them, or your firewall blocks them                   | Unban anyone banned by mistake    |
| Bot permission issue | The bot couldn't add them or assign the chosen role                       | Move the bot role above that role |
| Discord limits       | Discord slowed or refused specific adds                                   | Run another pull later            |
| Filtered             | A country, churn, left-server, retention or activity filter excluded them | Loosen or remove the filter       |

## Give it time

Pulls respect Discord's rate limits, so a big one runs gradually. RestoreCord adds no cooldown of its own on any plan, but Discord sets the pace. If your count is still climbing, wait for the pull to finish before drawing conclusions. The realtime migration log shows progress as it happens.

## Closing the gap

1. 1Post your new invite and verify link everywhere your community hangs out: socials, partner servers, your website.
2. 2Ask the members who are back to share it with friends who haven't returned yet.
3. 3Pin a short explanation in the new server so returning members know what happened.
4. 4From now on, make verification part of joining, so the next pull covers everyone.

Roles look wrong after a restore? Restored roles get new IDs. After a backup restore, RestoreCord keeps each member's saved roles waiting in a **Pending Role Restore** for a limited time, so run it once people are back.

Pending Role RestorePending

412 members have roles waiting to be restored · 968 role assignments · Expires in 6d 21h

View Details

Step 1

Backup restore finishes

Roles are recreated with new IDs; each member's saved roles are re-mapped and queued for 7 days.

Step 2

Banner appears

“Pending Role Restore” shows on the dashboard with member and assignment counts.

Step 3

Pull members first

Roles can only be assigned to members already in the server.

Step 4

Run Restore Roles

Runs in the background at Discord-safe rates; cancel any time, assigned roles are kept.

## Making the next pull complete

The single best thing you can do is lock your channels behind verification, so nobody can participate without becoming restorable. On Business and above, scheduled **OAuth authorization checks** regularly confirm members still authorize your bot and remove server access from anyone who revoked it, so your verified role always matches who you can actually pull. The whole setup is in [getting ready before members disappear](https://restorecord.wtf/before-members-disappear). Still not sure where people went in the first place? Try the [member drop diagnosis](https://restorecord.wtf/member-count-dropped), or go back to [RestoreCord Member Loss](https://restorecord.wtf/).

## Read your pull results

1. 1  
### Open the migration history  
Go to Dashboard, Migrations and open the pull you ran.
2. 2  
### Read each outcome  
Sort members into unauthorized, already in server, blocked, permission issues, Discord limits and filtered.
3. 3  
### Fix what you can  
Move the bot role up, loosen filters and unban anyone banned by mistake.
4. 4  
### Invite the rest  
Post your verify link where your community hangs out so missing members can come back and verify.
[Pull members documentation](https://restorecord.com/docs/guides/pull-members)

## Member pull questions

### 

### 

### 

## Make sure everyone is restorable next time

Put verification in front of your channels and every member becomes someone you can bring back.

[Set up verification free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
