Documentation
4. Notifications, Triggered Log & Managing Alerts
- Created
- Jun 12, 2026
- Updated
- Jun 12, 2026
This page covers what happens when an alert fires — how often, through which channels, where the history lives — and how to manage a growing set of alerts.
Trigger frequency
A condition can stay true for many bars, so each alert chooses how often a true condition may notify you:
- Once only — fire a single time, then stop. (The alert moves to a triggered state and can be restarted.)
- Once per bar — at most one notification per bar while the condition holds.
- Once per bar close — only when a bar closes with the condition true, never on the still-forming bar. See Realtime vs Delayed Data for forming vs confirmed bars.
- Once per minute — at most one notification per minute.
- Every time — every qualifying update, with a minimum re-trigger interval to avoid floods.
"A bar" means a bar on the alert's timeframe. For a condition that compares against an indicator, that's the Interval you choose in the dialog — e.g. an alert using a 5-minute VWAP counts 5-minute bars, so Once per bar fires at most once per 5-minute bar. A plain price condition (such as price crossing a level) has no interval, so it runs on a fine 1-minute timeframe and fires promptly when price crosses, regardless of the chart you're viewing — choose Every time if you want every tick.
Expiration
An alert can stop watching on its own: Open-ended (never expires), End of day, 1 week, 1 month, or a custom date and time. An expired alert stops evaluating and is marked accordingly.
Notification channels
Choose any combination of:
- Toast — an in-app notification in the top-right corner. Toasts stack, auto-dismiss after a few seconds, and can be swiped away or closed with the ✕.
- Browser notification — a system notification. The browser asks permission the first time; if you decline, alerts fall back to a toast.
- Sound — an audible cue when the alert fires. Because browsers block audio until you have interacted with the page, the cue becomes available after your first click or keypress in the app.
- Webhook — sends a
POSTwith a JSON payload to a URL you provide when the alert fires, so it can feed an external workflow. Delivery is best-effort and happens from your browser, so your endpoint must allow cross-origin requests fromhttps://fractalchart.com(a CORSAccess-Control-Allow-Originheader). Endpoints without it — including many off-the-shelf webhook receivers — will be blocked by the browser.
You can also restrict an alert to the regular session only, so equities alerts ignore pre/post-market activity.
The triggered log
Every time an alert fires, an entry is recorded in the Log tab of the Alerts sidebar, newest first. Each entry captures what fired — the alert's name, a summary of the condition, the price, and the time — so the history stays readable even if you later edit or delete the alert. A badge shows how many alerts have triggered. To tidy it up, hover a row and click the trash icon to remove a single entry, or use Clear in the Log toolbar to empty the whole log.
Managing a set of alerts
From the Alerts tab you can search by name, sort the list, and act on any row (pause/resume, snooze, stop/restart, clone, edit, delete — see Creating & Editing Alerts). Each row shows the alert's status and key details at a glance.
Storage, limits, and backups
Alerts and the triggered log are saved in your browser's local storage on one device:
- They persist across sessions but are not synced across devices or browsers, and are removed if you clear site data.
- You can keep a large number of alerts (up to 500); the triggered log retains the most recent entries (about 200) and rolls off the oldest.
- Export your alerts to a file and import them in another browser to move or back them up. (Presets and the triggered log are not part of the export.)
This local-first model matches the rest of the workspace — see how watchlists and other data are stored, and the storage note in the FAQ & Troubleshooting.
Next steps
That completes the Alerts guide. Head back to the start to explore other features.
Next: Introduction