Dry-Run vs Auto-Fix
Two independent network settings that control how aggressively the bot acts.
Two independent settings in Project settings control how aggressive the bot is. Both only exist for server networks — single-server projects always run live, so the toggles are hidden there.
- Dry-Run (Dry-run mode) — the bot logs what it WOULD do but doesn't change any roles. Perfect for testing new role rules on a live server without risk. Join roles from Auto Role are held back too.
- Auto-Fix (Auto-correct mismatches) — the periodic drift scan (every hour; every 30 minutes on Network and Grid) automatically corrects detected mismatches (member should have role X on sub-server Y but doesn't). If disabled, drift is only reported in the log channel; you decide what to fix manually. Live role sync is not affected by this setting.
What dry-run shows you
In dry-run, the log channel shows each change the bot would make, marked as a dry run. While it's on, the project shows as Test mode, and a banner with a Go live button sits at the top of every project page.
Even in dry-run, roles the bot can't assign because of the role order are reported ("Role can't be assigned"), at most once per role per day, and your admin role (if you set one) is pinged — that's something you need to fix before going live.
New network projects start with Dry-Run ON and Auto-Fix ON. While Dry-Run is on the bot changes nothing — so you can test safely. The moment you turn Dry-Run off, Auto-Fix is already active and keeps everything in sync automatically.