Recommended configuration
Include symbol, timeframe and indicator version in the name. Use the specific RamPath condition and Once Per Bar Close.
GUIDE · ALERTS
Create alerts with Once Per Bar Close and test delivery before relying on them.
Include symbol, timeframe and indicator version in the name. Use the specific RamPath condition and Once Per Bar Close.
TradingView, data, device, network and notification services can delay or miss an alert.
Read release notes and recreate alerts when the release says it is required. Never put passwords or personal data in webhook payloads.
Read the direct answer now. If your situation is different, Support will explain the software boundary and documented use.
Use Once Per Bar Close for the documented confirmed-bar workflow.
Not always. Release notes will state whether alerts must be recreated. TradingView alerts can retain the script state that existed when they were created.
No. Delivery can fail or arrive late, so alerts must not be the only risk control.
No. It is general analytical software. WATCH, ARMED, READY, CHECK and WEAKENING describe chart context; they do not choose a trade, contract, entry, quantity, target or stop.
No. Data, platform behavior, execution, leverage and user decisions can all materially affect outcomes.
Never. Access requires only the exact TradingView username. Support will never ask for passwords, OTPs, trading PINs or remote control of a broker account.
Start with the manual and FAQ, then open Support with the exact ticker, timeframe, version, date/time and Data status. Product support explains software behavior only.