Troubleshooting
If something looks off, use the checks below to confirm filters, sessions, and lifecycle states.
No confirmations showing
- Confirm your symbol and timeframe selections.
- Broaden filters to ensure you are not filtering everything out.
- Check whether you are viewing the correct session label (RTH or ETH).
- Confirm you are in Confirmation mode and not Context mode.
No context showing
- Switch to Context mode to view Forming or Pending opportunities.
- Confirm context stage filters include Forming or Pending.
- Remember that Context appears before Confirmation.
Filters behaving unexpectedly
- Symbols are comma-separated and case-insensitive. Empty means all symbols.
- Timeframes are 15m, 30m, 1h, 2h, 4h, D, 2D, 1W, 2W, 1M, 3M, 12M. Empty means all.
- Session filters apply only to intraday timeframes.
- FTFC min is numeric and FTFC must include toggles can require specific higher timeframes.
Confirmations expiring quickly
Confirmations expire on the next candle slot. They can also be invalidated if the pattern changes intrabar. This is expected behavior and part of the confirmation lifecycle.
No Telegram alert received
- Confirm your Telegram account is linked.
- Check that the preset has an active alert rule.
- Daily limits, cooldowns, or dedupe rules may suppress repeats.
- Confirm the alert is targeting the Context or Confirmation you are viewing.
How context and confirmations reach the UI
Data flows from the poller into the candle table. The worker runs scan_all, writes scanresult records for Context and Confirmation, and the API delivers them to the UI. History is stored as new scanresult entries. Price snapshots are produced by the worker and saved to pricesnapshot with in_force and invalidation states.
No financial advice
STRAT Scanner is for educational and informational use only. It does not provide financial advice.