Repeated alerts train you to ignore alerts, which defeats the purpose entirely. Four causes account for nearly all of them.
1. The trigger is set to "Once per bar"
This is the big one. "Once per bar" fires every time the condition is true during a bar — and a condition like price above 100 is true on every tick while price stays above 100.
Switch to "Once per bar close" and you get one alert per candle, after the candle confirms. For most conditions this is what people actually wanted. Use "Only once" for a level you only need to be told about a single time.
2. You created the alert more than once
Open the alerts panel and read the full list rather than the last few entries. Duplicates accumulate easily: an alert created from two layouts, or recreated after you assumed the first one had expired.
Sort by symbol, and delete everything you can't explain. If you keep several similar alerts deliberately, rename them — an alert called "ES 15m close above range high" is obvious; three alerts called "Alert on ES" are not.
3. Multiple delivery channels for the same alert
One alert with app push, email and a webhook enabled is one trigger arriving three ways. It looks like three alerts.
Open the alert's notification settings and keep only the channel you actually read.
4. The condition oscillates around a level
A condition like RSI crosses 70 can cross back and forth repeatedly while RSI hovers right at the level. Each crossing is a genuine, separate trigger.
Fixes:
