The watchlist ranks tracked setups best-grade-first, each row carrying its last grade, signal, confidence, direction, price, scan time and distance to trigger. A re-scan runs the full engine on fresh data with persistence off: scans never enter the journal or the outcome statistics.
Rows and ranking
Best grade first, so the list answers "what is closest to worth doing" rather than "what did I add most recently". A row close enough to its trigger level is marked as at trigger.
What a re-scan does — and does not do
A re-scan is the full engine on freshly fetched candles. It refreshes the row.
It is explicitly not a decision. Scans run with persistence off, so nothing about them reaches your journal or the event-log statistics. Only decisions you take on the Analyze desk enter the record — otherwise a trader who left the watchlist open would accumulate hundreds of phantom rows they never chose.
Row lifecycle
A Watch decision taken on the Analyze desk lands here with an alert already armed at the first target. Removing a row disarms any alert attached to it, so a deleted row cannot go on firing notifications for something you stopped tracking.
Frequently asked
- Do watchlist re-scans show up in my journal?
- No. Scans run with persistence off — they refresh the row from fresh data but never write to the journal or the outcome statistics. Only decisions you take on the Analyze desk enter your record.
Updated Sep 1, 2026