Learn to save reusable criteria, choose a default, preview alert rules, configure delivery, and control noise.
Save repeated search choices so you do not have to enter them again each day. A saved filter restores criteria on the page that supports it. An alert rule is a separate set of monitoring and delivery choices; saving a search does not automatically enable notifications everywhere.
Name filters by strategy and horizon, then preview a rule before enabling delivery.
What the page shows
Field or control
How to use it
Saved filter name
Identifies the strategy and should make its purpose clear to your future self.
Filter definition
Stores supported criteria such as symbols, signal families, scores, and other page-specific controls.
Default filter
Loads automatically where supported; changing it does not rewrite other saved filters.
Rule templates
Provide starting configurations that still require review.
Rule preview
Replays available historical data to estimate match behavior; it is not a backtest or performance promise.
Frequency and cooldown
Limit repeated notifications for the same symbol or event.
Channels and quiet hours
Control supported in-app, email, Telegram, push, or webhook delivery and timing.
Rule state and history
Enable, pause, inspect, edit, or remove rules and review delivered events.
Recommended workflow
Build and validate the filter on its owning page.
Save it with a strategy, market, and horizon in the name.
Create or choose an alert rule and inspect every condition.
Use preview to detect excessive or empty matching.
Set cooldown, channels, language, and quiet-hour behavior.
Enable the rule and confirm delivery with non-sensitive test tooling where available.
Review outcomes and pause stale rules instead of continually widening them.
How to interpret the result
A preview estimates frequency from available history; it does not measure future returns.
No notification can mean no match, disabled delivery, stale data, or a channel problem.
A default filter changes initial page state, not the canonical market data.
Common mistakes
Creating broad rules with no cooldown.
Treating a notification as an order instruction.
Forgetting device, email, Telegram, push, or webhook configuration.
Deleting a filter that an active workflow still expects without reviewing dependencies.
Risk and limitations
Rule evaluation and delivery depend on source data, scheduled workers, networks, providers, and device permissions. Missed or late notifications remain possible.
Saving a filter makes search choices ready for your next visit. Creating an alert rule asks the system to monitor conditions and send matches through selected channels. Do not assume that saving any filter on any page automatically enables notifications.
