Alerts
Create value, event, asset, and geographic monitors from the map, Radar, or an asset page.
Choose where to begin
Start from the thing you want to monitor. Ask the Grid carries its context into the alert instead of asking you to rebuild it.
From the map
Select a price node or asset and choose Set alert from its info card. For a place rather than an asset, drop a pin and create a radius alert. Multi-select can carry a chosen set of nodes into one area rule.
- 1Open a live grid and select an asset, node, pin, or group.
- 2Choose Set alert from the contextual action.
- 3Review the scope at the top of the right-side alert panel.
From Radar
Use a widget's alert action to monitor the metric in place. The grid, metric, current value, and a sensible starting threshold are added to the draft automatically.
From an asset page
Use Set alert on an individual asset page when you want the rule permanently tied to that facility or settlement point.
From the Alerts manager
Open Alerts in the main navigation to start from a suggested job: a node price, system load, grid event, weather condition, asset change, or a custom rule.
Value alerts
Use a value alert when the job can be expressed as a metric crossing or departing from a meaningful reference.
Fixed threshold
Trigger when a supported metric goes above or below a number—for example, nodal LMP above $100/MWh or ERCOT system load above 75,000 MW.
- 1Choose the metric and Above or Below.
- 2Enter the threshold in the metric's displayed unit.
- 3Choose how much evidence is required before the rule activates.
Change, baseline, and forecast jobs
The alert model is designed to extend beyond fixed numbers: percent change, deviation from a moving baseline, forecast-versus-observed error, and anomaly bounds are natural value-alert jobs. The beta only shows condition types backed by a live evaluator for the selected source.
If a condition is not offered for the selected metric, the evaluator does not support it yet; do not translate it into a misleading threshold.
Lookback and confirmation
Lookback controls the evidence window. Confirmation controls how many consecutive evaluations must match before the alert activates. Increase confirmation for volatile metrics to avoid reacting to a single interval.
Recovery
Recovery defines when an active alert returns to normal. Use a separate recovery threshold when the metric tends to hover around the trigger; this prevents repeated activate/recover notifications at the boundary.
Event alerts
Use an event alert when the important change is a new occurrence, notice, or status—not a numeric crossing.
Grid events
Watch for outages, operator notices, reliability actions, and other supported operational events. Scope the rule to a grid, asset, selected set, or geographic area, then filter the event categories and severity that matter.
Asset changes
Asset-scoped jobs include new operational information, status changes, and newly associated events. The notification identifies the asset and the new evidence rather than reporting a generic grid event.
New entities in an area
Area and grid scopes are the foundation for monitoring new entities or assets as coverage expands. This is a product direction; the beta only offers event types currently backed by the evaluator and source data.
Geographic alerts
Geographic scopes turn a location or collection on the map into something that can be monitored over time.
Pin and radius
Drop a pin, choose a radius, and watch for supported events near that location. The radius stays visible while you configure the condition so the monitored footprint is clear.
Multi-select
Select several nodes to monitor them as a fixed set. This is useful for a portfolio, corridor, development screen, or operating footprint that does not form one simple radius.
Lasso and custom areas
Lasso and richer custom-polygon rules are part of the geotemporal direction. They should preserve the selected geometry, membership behavior, and map evidence; they are not implied to be live unless the composer offers them.
Delivery and access
Enable the beta
Alerts is an opt-in experiment. After signing in, enable Alerts under Settings → Experiments. The choice is saved to your account, so the Alerts manager and contextual alert actions appear on every signed-in device.
- 1Create or sign in to a free account.
- 2Open Settings, then choose Experiments.
- 3Turn on Alerts. You can also enable it from the Alerts preview page.
Turning the experiment off pauses every active rule. Re-enabling it does not automatically resume those rules.
Email is included with Free
A free account is required because an alert runs after you leave the page and needs a verified destination. Activation, recovery, source-health, and test notifications are delivered to the verified account email.
- 1Enable the Alerts beta for your account.
- 2Review the email shown under Notify.
- 3Save the rule, then use Send test email from its expanded row if you want to verify delivery.
Control notification volume
Value rules are episode-based: a true condition does not email on every one-minute evaluation. Each rule also has a rolling 24-hour email cap for repeated episodes or bursts of distinct grid events. Ask the Grid keeps recording triggers in Activity after the cap is reached, so delivery protection never removes evidence.
- 1Choose Emails / 24h under Notify.
- 2Use a lower limit for noisy exploratory rules and a higher limit for critical event streams.
- 3Review capped triggers in Alerts → Recent activity.
Slack and custom destinations are Enterprise
Enterprise workspaces can route team alerts to Slack channels and custom notification endpoints. The beta presents this as an upgrade path; Slack delivery itself is being rolled out separately.
- 1Open the Slack or custom destination callout under Notify.
- 2Choose Talk to us to open the notification-specific Enterprise path.
Why sign-in is required
Anonymous visitors can inspect the public grid, but persistent alert state, delivery destinations, and evidence history belong to an account. The signup gate shows the feature in context and returns you to the alert draft after authentication.
Manage and troubleshoot
Understand rule health
Healthy means the evaluator can read the source and run the condition. Degraded or error states describe source or evaluation trouble separately from whether the monitored condition is active.
Read evidence history
Recent activity combines transitions across every rule into one chronological feed. Expand a rule for its focused evidence history. Both views retain observed time, source, value when available, and delivery status—including triggers recorded after an email cap was reached.
See alert activity in Radar
Radar → Events includes an Ask the Grid alerts widget filtered to the current ISO. It sits beside the operator event stream, so a user can compare what the grid reported with which personal rules actually triggered.
Pause, clone, or archive
Pause stops evaluation without deleting the rule. Clone creates a paused copy for safe editing. Archive stops evaluation and removes the rule from the active manager while retaining service-side evidence.
Missing data
Choose how the rule should treat a delayed or missing source. Missing data is not automatically normal and should not silently resolve an active condition.
If a rule is degraded, inspect its source timestamp and health message before changing the threshold.