How should I version Pine strategies and webhook alerts?
Give strategy releases, alert instances and webhook schemas explicit versions. Versioning lets support and audit logs prove which logic produced a live signal and prevents silent incompatibility after script changes.
What this means in practice
Give strategy releases, alert instances and webhook schemas explicit versions. Versioning lets support and audit logs prove which logic produced a live signal and prevents silent incompatibility after script changes. This page is specifically about “How should I version Pine strategies and webhook alerts?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — Strategy v3.5 to v3.6
Inspect the mechanism named by “Scenario A — Strategy v3.5 to v3.6” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario A — Strategy v3.5 to v3.6 on question 54, use that evidence specifically to answer “How should I version Pine strategies and webhook alerts?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — Webhook schema change
Inspect the mechanism named by “Scenario B — Webhook schema change” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — Webhook schema change on question 54, use that evidence specifically to answer “How should I version Pine strategies and webhook alerts?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Support investigates historical trade
Inspect the mechanism named by “Scenario C — Support investigates historical trade” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Support investigates historical trade on question 54, use that evidence specifically to answer “How should I version Pine strategies and webhook alerts?”; keep it separate from the evidence for the other scenarios on this page.
What to check
- TradingView alert log and exact send time
- HTTP status and receiver timestamp
- validated payload plus signal ID
- cTrader result only after transport is proven
Practical rule
For “How should I version Pine strategies and webhook alerts?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.
Decision summary
Direct answer: Give strategy releases, alert instances and webhook schemas explicit versions. Versioning lets support and audit logs prove which logic produced a live signal and prevents silent incompatibility after script changes.
Next action: Match the observed evidence to one scenario above, test that mechanism independently on demo and keep the result traceable with one signal ID.
Primary sources
Need a TradingView → cTrader execution route?
NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.