Admitted viewers read permitted activity; commissioners add notes under configured policy.
All phases; events may be pending, saved, failed, corrected, or final.
HELP TOPIC // league
/activity-and-commissioner-notes · corpus 0.1 · verified 43c1c50
Activity and Commissioner Notes
Distinguish manager actions, processor results, commissioner rulings, and notification receipts.
Sources
Who can use this answer.
Read the current gate
Owning league instance and activity visibility policy.
The label carries the consequence.
Loading, empty, saved, pending, failed, permission-denied, stale, unavailable.
Use the runtime clock
Events show runtime timestamps and league-local timezone.
Keep the right audience
Activity filters private team data by viewer authorization.
Take the next safe step.
- →
Open Activity after consequential actions.
- →
Identify actor class, object, outcome, and receipt.
- →
Treat notes as context, not replacement for runtime.
- →
Follow owning route for current action.
Know what changes.
What happens
A receipt records persistence; a queued notification is not delivery proof.
What can be undone
History is append-oriented; corrections create explicit follow-up events.
What you should see
Entries identify saved/pending/failed/corrected/final state and route.
Keep context. Do not replay blindly.
Partial reads label unavailable pages and preserve unaffected entries.
Refresh owning route and compare latest receipt; escalate suspected mismatch.
One concrete read.
Example: A waiver award and commissioner correction are separate actor-class events.
Runtime source: Persisted activity/audit events, processor receipts, notes, notification receipts.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.