Skip to content

docs(admin): say what pending state actually costs #12

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

Merged
MrAlders0n merged 1 commit into from
Aug 2, 2026
Merged

docs(admin): say what pending state actually costs #12

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
2 changes: 1 addition & 1 deletion docs/admins.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -320,7 +320,7 @@ That catalog is what makes [Pending Repeater Links](#pending-repeater-links) wor
When enabled, newly discovered repeaters will enter a **Pending** state instead of **Active**. Pending repeaters are hidden from the map until an admin reviews and approves them, and are resolved automatically once they have been in the queue for 3× the stale timer — see [Pending repeater resolution](#pending-repeater-resolution) for exactly how that decision is made. In multiregion mode, this setting is configured per-region under Region-Specific Settings.

!!! warning "Data Inaccuracy Warning"
New repeaters will not display on the map until approved. This can cause data inaccuracies. Use with caution.
Pings are not associated to a repeater until it has been approved and set to **Active**. Any coverage heard while it sits Pending stays unlinked, and approving it later does not backfill those pings — use **Reassociate Repeater** in the Tools tab if you need them attached.

#### Disable Duplicate ID Detection Logic

Expand Down