Filtering Status
A live operational summary of the token universe currently held by the filtering engine, including data coverage, passed candidates, open positions, blacklists, and the filters rejecting the most tokens.
Refresh
Live metrics every 5 seconds
Coverage
Pricing, OHLCV, and positions
Outcome
Passed and blacklisted totals
Diagnosis
Top rejection reasons by source
What the Status tab is for
Use Status for a fast health check. It tells you whether discovery is supplying tokens, whether enough tokens have usable pool prices and OHLCV history, how selective the active rules are, and which source is currently responsible for most rejections. The dashboard polls these figures every five seconds.
Reading the interface
Each area answers a different operational question. Use the descriptions below before changing a filter.
Coverage metrics
These numbers describe how complete the filtering snapshot is before you judge pass rate.
Total Tokens
The number of token records represented in the current filtering cache.
With Price and With OHLCV
Separate coverage signals for live pool pricing and historical candles. They serve different parts of ScreenerBot and should not be treated as the same dataset.
Last Refresh
Shows the age and timestamp of the current snapshot. A stale value is a data-flow problem, not evidence that every token failed.
Decision metrics
These values show what happened after the active filtering rules were applied.
Passed Filters
Tokens that survived every enabled stage and can be considered by downstream trading logic.
Blacklisted
Tokens blocked by blacklist state. Blacklisting is distinct from an ordinary threshold rejection.
Open Positions
Tokens already held in active positions. This gives context when filtering rules change while a trade remains open.
Rejection breakdown
The right side ranks current rejection pressure without requiring you to inspect tokens one by one.
Source totals
Pills group rejections by Core, On-Chain, DexScreener, GeckoTerminal, RugCheck, or AI when enabled.
Top reasons
The most common human-readable rejection reasons are ranked with counts and proportional bars.
What Status cannot tell you
Status is a snapshot overview, not a historical analysis or token-level investigation tool.
Use Analytics for trends
Analytics compares pass and rejection behavior across a selected time range.
Use Explorer for individual tokens
Explorer lets you select a rejection reason and inspect the matching token records.
Recommended workflow
- 1
Check Last Refresh first. If the cache is stale, investigate data flow before changing thresholds.
- 2
Compare Total Tokens with With Price and With OHLCV to identify missing-data pressure.
- 3
Review the passed rate and source totals to see whether one filter family is dominating.
- 4
Open Analytics for time-based context or Explorer to inspect the actual rejected tokens.
Practical guidance
- A low pass rate is not automatically a problem; it may be the intended result of strict risk controls.
- A sudden increase in missing-data rejections usually points to source availability or enrichment lag.
- Change one setting family at a time, then watch Status before making another adjustment.