BTA / Delivery desk
Alert Configuration Snapshots and Rule Drift
The chart you see today may not describe the alert instance still running.
Save the running instance, not just the chart
TradingView states that an indicator alert can continue using the settings present when it was created after chart inputs change. Preserve the active instance's condition, interval, inputs and lifetime. A screenshot of the current chart is not a substitute for that historical configuration. Other workflows need their own documented instance semantics rather than a borrowed assumption.
Identify the script or strategy version where available. Record data inputs and whether the condition evaluates a completed observation or an evolving one. A human-friendly alert name may be reused; keep the stable instance reference as well. The evidence should identify the object that actually generated the message.
Changes need a new boundary
A rule change can begin a new observation population. Do not combine old and new instances into one apparent performance sample without disclosing the transition. Retain stopped, expired and replaced instances. An alert that no longer fires might have reached its lifetime boundary rather than suffered transport failure.
When testing, freeze settings before sending or observing the declared set. If a configuration change is necessary, preserve the reason and effective time. A favourable historical chart should not be used to reconstruct what a different earlier instance would have emitted in real time.
Interpret the evidence narrowly
A complete saved configuration can make an event reproducible in meaning without proving delivery or account execution. A complete receipt log can show what arrived without identifying the correct generating instance. The reviewer needs both where the claim concerns that relationship.
BTA's evidence form asks for an instance snapshot and data-availability record because these objects answer different questions. Entries remain unverified reader notes. A documented platform rule does not validate a private script or establish that its historical markers were available at the claimed decision time.
Original Evidence Packet
| Artifact | Record to retain |
|---|---|
| Instance | Condition, inputs, interval, version and lifetime |
| Transition | Old/new boundary and retained replaced instances |
| Observation | Original live event rather than later chart |
Continue the Investigation
Source Boundaries
Official references describe published mechanisms. BTA's evidence packets and proposed test procedures do not claim a completed paid-feed or account trial.