Easy Auth
/reconcile

How do I fix members after the bot was offline?

When Easy Auth is offline it does not see the members who join or leave, and a server it was just added to already has members it never processed. The /reconcile command brings the stored records and roles back in line with the real member list, and it never punishes anyone.

When you need it

Easy Auth keeps a record for every member and reacts as people join and leave. Two things leave that record out of step with who is actually in your server:

  • The bot was offline for a while. Members who joined while it was down have no record and never got the unverified role, and members who left are still counted as present.
  • You just added Easy Auth to a server that already has members. Everyone who was there before the bot arrived is unknown to it.

In both cases you do not have to touch anyone by hand. /reconcile compares the real member list with what Easy Auth has stored, and brings the two back in line.

Run it

/reconcile is a staff-only command: you need the Manage Roles permission to use it. It does not change anything on its own. First it shows you what it found and what it would do, and waits.

Commands matching /reconcile

/reconcile

Align member records and roles with the current members

Easy Auth
/reconcile

Start typing /reconcile and pick it from the list. Only members with Manage Roles can use it; anyone else who tries gets a permission error.

  1. Run /reconcile. Easy Auth replies only to you, with a summary of what it would change.
  2. Read that summary. Each line is one kind of change, with a count.
  3. Press Confirm to apply it, or Cancel to do nothing. Until you press Confirm, nothing has changed.
Easy AuthAppToday at 21:04

Reconcile Members

• Create 12 missing records (new members)

• 2 of those would fail the Join Gate now (reported, not punished)

• Fix 3 records (record incomplete)

• Mark 5 records as left (member no longer here)

• Auto-verify 2 trusted members (whitelist or rejoin)

• Reconcile 4 rejoins (1 must verify again, 3 timers restarted)

• Assign the unverified role to 10 members (~5s)

• Give the verified role back to 2 verified members (~1s)

• 3 members have the verified role but no verification record (reported, not changed)

⚠️ 4 members are already past the unverified time limit and will be punished right after this. Verify anyone you want to keep first with /verifyall.

No one is punished by this. Proceed?

ConfirmCancel
Only you can see thisDismiss message

The confirmation Easy Auth shows before doing anything: one line per kind of change it found, then a warning if any member is already past the time limit. Nothing happens until you press Confirm.

The summary always ends with No one is punished by this. Proceed? — the command never kicks, bans or blocks anyone. On a large server the last part can take a few minutes, because roles are handed out slowly to stay within Discord's limits. If it runs long, Easy Auth posts the result in your log channel and pings you, so you can close the command and carry on.

Verify anyone you want to keep first

If your server is Premium and uses the unverified time limit, giving these members a record is what lets the timer count them. Any who are already past the limit will be punished by the timer shortly after /reconcile runs. The prompt warns you with the exact number. Verify the people you want to keep before you confirm, with /verifyall, then run it.

What it puts back in order

When you confirm, Easy Auth works through the member list and reports what it did. Each line appears only if there was something to do:

  • Records created: members it had never seen start being tracked, so their verification state, timers and log entries now count from here on.
  • Records fixed: a record that already exists but is incomplete, usually missing the join date it never got, for a member who is here on the same visit. The record is completed, not reset.
  • Members marked as left: members who left while the bot was offline are no longer counted as present.
  • Members auto-verified: trusted members who should have been let in on the way in are verified now. These are people on your whitelist, and members who left and came back inside your automatic rejoin window.
  • Rejoins reconciled: members who came back have their verification timers restarted from the real moment they rejoined. Someone who came back too late to keep their old verification has to verify again.
  • Unverified roles assigned: unverified members who were missing the unverified role get it. This part is skipped if you have no unverified role set, or if the bot cannot assign it.
  • Verified roles restored: members who count as verified but no longer have the verified role get it back. That happens when the role was taken away by hand while the bot was offline, or when the bot could not hand it out at the time because it sat too low in your role list.
Easy AuthAppToday at 21:04

Reconcile Members

📄 Records created: 12

🔧 Records fixed: 3

👻 Members marked as left: 5

✅ Members auto-verified: 2

🔄 Rejoins reconciled: 4

🎭 Unverified roles assigned: 10

🎭 Verified roles restored: 2

Only you can see thisDismiss message

The report at the end, one line per kind of change. A line is left out when its count is zero, so a tidy server shows only a few.

Members who are already fine are left alone. If some roles could not be assigned, the summary says so and points at the bot's permissions and role position, which the guide on the verified role covers. Nothing is invented: the command never back-dates a join, so your history and analytics stay honest.

The Join Gate review list

/reconcile also checks the members it just created a record for against your Join Gate, and it never acts on them. Removing someone who has been in your server for weeks would be a nasty surprise, so instead it lists them in a second message, Join Gate Manual Review, grouped by the check they would fail. You decide what to do with them.

Easy AuthAppToday at 21:04

🚧 Join Gate Manual Review

New members that would fail the Join Gate right now. Nothing was done, so review them:

No profile picture: @blank-slate

Account too young: @just-made-this

Only you can see thisDismiss message

The review list arrives together with the summary. It only names members, grouped by the check they failed, and takes no action on any of them.

It judges each member on their profile as it is now, not on the day they joined. So a long-time member whose account is old by now, with an avatar and a normal name, is not flagged, even if their account was brand new when they first arrived.

Members you gave the role by hand

Handing someone the verified role yourself counts as verifying them, and Easy Auth records it that way as soon as it sees it happen, with your name against it. Seeing it needs the bot online and the View Audit Log permission, which /diagnose checks for you.

When it could not see it, that member keeps the role without ever becoming verified in the records. Nothing is taken away from them for it: on a Premium server with a time limit, Easy Auth records them as verified when their window runs out, instead of punishing them.

/reconcile lists them and changes nothing, because the answer depends on your server: on some, that role has been the everyday member role for years.

Easy AuthAppToday at 21:04

🎭 Verified Role Without a Record

Members with the verified role but no verification record. I left them as they are, so decide:

@early-bird @old-timer @quiet-one

Verify them: /verify for one, /verifyall with @Verified as the role for all

Or take the role back: /unverify

Only you can see thisDismiss message

The second review list, sent together with the summary. It names the members while there are fifteen or fewer of them, and gives you the count above that.

Settle each of them one way or the other, because leaving them as they are settles nothing: they hold the role while Easy Auth does not count them. Verify a single member with /verify, or the whole list with /verifyall and the verified role picked in the role option, which leaves everyone else alone. If someone should not have the role, /unverify takes it back.

Still stuck after the guide?

Ask in the support server: bring your server ID and what the bot did instead of what you expected. Billing, refunds and account issues start there too.

Ask in the support server