Notifications & Resets

A Prysm alert has a short life. It waits for a condition, fires once, and then either disables itself or re-arms against a fresh baseline depending on the type. This page covers what happens at the moment of firing and afterwards — how the notification looks, which alerts come back, and what manual actions reset them.

How alerts fire

Two paths can trigger an alert; they run independently and reach the same outcome.

Path	When it runs	What it watches
Scheduled check	Periodic cron sweep of every active alert	Batch-fetched price + market cap for each tracked token
Real-time stream	Live price updates for tokens whose pool the bot is watching	Price ticks pushed the moment a swap settles on-chain

The scheduled check is the baseline — every alert is evaluated on a fixed cadence. The real-time stream is an extra fast path for tokens with enough active alerts and a known DEX pool on a chain that supports live data: percent-change alerts fire near-instantly there, and price/market-cap alerts get the same treatment if at least three alerts on the same token justify the connection.

You don’t pick which path. The bot does it automatically. Either way, the firing logic is identical:

Price alert — fires when the current price crosses the target in the configured direction (>= for above, <= for below).
Market cap alert — same logic, against the live market cap computed from current price × circulating supply.
Percent-change alert — fires when the absolute change from the alert’s baseline price reaches your target percentage, in either direction.

What a fired notification looks like

The notification arrives as a Telegram DM from the bot. The format depends on the alert type.

Price and market-cap alerts

🚨 Price Alert

🚨 Price Alert Triggered! 🚨

🔹 PEPE (Pepe)

Price is now above your target!

Alert Details:
Target: $0.0000123
Current: $0.0000128

Token Address:
0x6982508145454ce325ddbe47a25d4ec3d2311933

This alert has been deactivated.

The chain emoji on the token line is the real chain emoji from Prysm’s custom-emoji set — 🔹 for Ethereum, Base, MegaETH; 🪙 for Solana; 🔸 BSC; 🟣 Polygon; 🔺 Avalanche; 🔷 Arbitrum; 🔴 Optimism and Tron; 💎 TON; 🌊 Sui; ⚡ Sonic. The SYMBOL (Name) text on that line is a clickable link that opens your preferred chart provider.

“Market Cap” replaces “Price” in the header line for market-cap alerts; everything else is the same.

Percent-change alerts

These use a tighter, single-line format because they’re built to re-arm and fire repeatedly:

📈 Percent Change

🪙 BONK (Bonk)

📈 MCap: $1.8B | $0.0000245 | +5.21%

The arrow is 📈 when the move is up, 📉 when it’s down. The percent is the move from the alert’s baseline at the moment it last armed (which, for a re-firing alert, is the price at the previous trigger). The ticker is again clickable and opens your chart provider.

One-shot or recurring?

This is the most important behaviour to understand. The two flavours do different things after firing.

Alert type	After firing	Re-arms automatically?
Price	Marked triggered, deactivated	No
Market cap	Marked triggered, deactivated	No
Percent change	Marked triggered, baseline reset to current price, stays active	Yes — fires again on the next ±target% move

Price and market-cap alerts are one-shot. They tell you “this level was hit” once, then they’re done. The notification’s closing line — “This alert has been deactivated.” — says so explicitly. The alert no longer counts against your active-alert quota and won’t appear in /alert until you re-create or edit it.

Percent-change alerts are recurring by design. When one fires, the baseline moves to the price at the moment of firing, and the same ±target% threshold is now measured from that new starting point. A ±10% alert that fires at $0.10 silently resets its baseline to $0.10; the next notification will come when the price reaches $0.11 (+10%) or $0.09 (-10%). It keeps doing this indefinitely until you remove it.

Editing a fired alert re-arms it

If a price or market-cap alert has already fired and you want it back on duty, the simplest way is to edit it. The edit deep link from the /alert overview prompts you for a new target value, and saving that value flips both flags back on:

isTriggered returns to false
isActive returns to true

So an edited alert is automatically re-armed, even if it had already fired and gone dormant. You don’t need to delete and re-create it. This works for any alert type, but it’s mainly useful for the one-shot ones — percent-change alerts re-arm themselves anyway.

The edit flow lives behind the ✏️ pencil emoji on each row in /alert. See Manage Alerts for the full walkthrough.

Where fired alerts go

/alert only lists alerts where isActive = true. That means:

A price or market-cap alert disappears from the overview after firing. Prysm treats it as retired; the DM is the record.
A percent-change alert stays in the overview after firing, with its baseline silently updated. The displayed ±X% is unchanged — what moved is the price the threshold is measured from.

There’s no separate “history” view for triggered one-shot alerts. The DM notification is the record.

Removing a token deletes its alerts

/remove triggers a cascade clean-up. If no other user and no group is still tracking the token, Prysm deletes the token row entirely and every price alert tied to it goes with it — yours and everyone else’s. If somebody else is still tracking it, the token stays and your alerts on it stay too (remove them through /alert).

The rule of thumb:

Removing a token you’re alone on wipes its alerts.
Removing a token others still track leaves your alerts in place.

Notification deduplication and cooldown

There’s no explicit cooldown timer in the alert engine. Whether you get spammed depends on the type:

Price and market-cap alerts can’t oscillate because they deactivate after the first fire. One notification per alert, ever, until you edit or re-create it.
Percent-change alerts can fire as fast as the price moves through ±target% from each new baseline. Because the baseline jumps to the trigger price every time, a slow ramp through 5% won’t re-fire — the move has to clear another full target% from where it last paused.

A few internal guards prevent edge-case spam: percent-change checks skip if the current price is zero (so a dead or migrated pair doesn’t flood you with -100% alerts), and absurd computed changes are dropped.

What can stop an alert from firing

The bot delivers nothing if any of these are true:

The alert is inactive (already fired and one-shot, or manually deleted from /alert).
The token’s price feed is unavailable on the scheduled tick — the alert is skipped for that round and re-evaluated next time.
For market-cap alerts: the token’s circulating supply isn’t known, so the live market cap can’t be computed.
You blocked the bot or your DM is closed. The alert is still marked triggered on the bot’s side and won’t fire again on its own.

In normal operation none of these matter — they’re listed here so the behaviour is documented when something does go wrong.

Where to next

Create an Alert The /setalert flow plus the inline 🔔 and 📊% buttons in /detailed.

Manage Alerts Edit values, remove rows, and read the /alert overview.

Alerts overview The three alert types side by side and when to reach for each.