Inspect why tokens stopped in the filter chain
Browse non-blacklisted tokens rejected by the current snapshot and narrow the list by rejection reason.
Decision
First failed enabled rule
Excludes
Blacklisted tokens
Control
Reject Reason filter
Evidence
Readable label and raw code
What the Rejected tab is for
Rejected contains tokens that stopped at the first enabled rule they failed. It adds a Reject Reason column and server-backed reason filter, complementing Filtering Analytics and the Rejection Explorer.
Reading the interface
Use membership, coverage, and actions together before drawing a conclusion about a token.
Understanding rejection
The reason records where current evaluation stopped.
First failure wins
Later stages do not run after an earlier enabled rule rejects the token.
Readable reasons
Machine codes are translated while the raw reason remains available in the full value.
Reason filter
Compare tokens rejected by the same condition.
Investigating patterns
Use evidence before editing thresholds.
Filtering Explorer
Inspect tokens, source, reason, and timestamp.
Filtering Analytics
Measure rejection reasons and sources over time.
Recommended workflow
- 1
Choose one rejection reason.
- 2
Compare market and security values.
- 3
Verify the pattern in Explorer and Analytics.
- 4
Change one filter family and observe the result.
Practical guidance
- Manual Buy does not make a rejected token a passed candidate.
- Missing-data and unsafe-data rejection require different responses.
Do not weaken filters only because a familiar token was rejected. Verify the source data and configured threshold first.