An authorized manager with roster capacity and an eligible player action.
The current league waiver mode; unsupported/source-unavailable modes are labeled.
HELP TOPIC // players
/players-free-agents-waivers-and-faab · corpus 0.1 · verified 43c1c50
Players, free agents, and waivers
Acquire an eligible player using this league's own configured claim rule — priority order or FAAB bid — and preserve filter context.
Sources
Who can use this answer.
Read the current gate
Team association, capacity/position eligibility, acquisition capability, and priority/FAAB units.
The label carries the consequence.
Free-agent-available, waiver-locked, claim-draft, claim-submitted, pending-run, processing, awarded, lost, canceled, roster-ineligible, insufficient-FAAB, priority-unavailable, source-unavailable.
Use the runtime clock
Exact waiver clear/process time, timezone, and relative text come from runtime.
Keep the right audience
Claims/bids follow configured visibility; never expose another team's private bid.
Take the next safe step.
- →
Read pool freshness and eligibility.
- →
Add a true free agent before their own kickoff, even after Thursday's game starts; file a claim for a dropped player or one whose game has started.
- →
Enter non-currency FAAB units when configured.
- →
Review drop, priority, and submitted state.
- →
Cancel/reorder only while permitted.
Know what changes.
What happens
A claim is revalidated at processing; capacity, ownership, eligibility, and units may change.
What can be undone
Edit/cancel only before the displayed boundary; awarded movement follows runtime finality.
What you should see
Submitted/awarded/lost/canceled reason and player/filter context are shown.
Keep context. Do not replay blindly.
Validation, stale, insufficient units, capacity, source, and permission failures spend nothing.
Return to Players with waiver filter; reread state/last success before retry/cancel.
One concrete read.
Example: Two claims can be submitted before processing; the configured priority or units decide the recorded result.
Runtime source: Acquisition config, pool, roster, claim queue, processor clock, source freshness.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.