TradingView: Alert Workflow and Delivery Evidence

An alert carries a configuration history

TradingView notes that an existing indicator alert can retain old settings after the chart's indicator inputs change. Save the alert configuration itself, not merely a screenshot of the current chart. A rule on one interval may not describe an alert running on another.

Separate a trigger from a delivered instruction

Define whether the rule observes live price changes, bar completion or strategy events. Check Pine repainting behaviour when historical signals look different from live observations. Record trigger time, notification receipt and any downstream acknowledgement as separate events; a visual marker alone does not prove delivery.

Inspect failure handling

Track expired alerts, disabled notifications and duplicate messages in the same log as successful deliveries. If a webhook feeds an order system, require a clear retry, rejection and duplicate policy. We did not test a paid account, private script or connector; the public documentation cannot establish the reliability of an arbitrary user's chain.

Delivery Investigation for This Product

Useful when you can specify the rule, interval and alert lifetime and retain those settings.

Documentation can establish a published mechanism while private account behaviour remains unobserved. Confirm the selected plan, supported destination and authority directly. A complete notification is not an order confirmation.

Keep a route-specific evidence record / Proposed safe delivery-test protocol