Common Pine Script Futures Webhook Mistakes

These defects compound. A broad `close > average` condition can emit repeatedly; a qualifying receiver 5xx can then resend each event; an incorrect quantity or symbol can amplify the result across a live account. Fixing only the JSON would leave the event defect intact. A prevention checklist should move in causal order: decide what event exists, decide when it may emit, construct the message, validate the route, calculate exposure, and verify external execution.

Most failures are observable before money is involved. TradingView exposes alert events and Webhook status, Pine can render test messages, and HexTrade documents `dryRun: true` for planned validation without sending an order. Use those tools to reject ambiguity. A live smallest-size test remains necessary because dry mode cannot prove broker authorization, current contract availability, order support, protective behavior, or a fill.

`alertcondition()` creates functioning triggers in indicators, requires global scope, and accepts a constant message with supported placeholders. `alert()` works in indicators and strategies, executes where its local code path is reached, and accepts a dynamic series string. Strategy order-fill events require a strategy and occur when TradingView's broker emulator executes a simulated order. Each can produce useful JSON, but their event timing and alert-dialog configuration differ.

A common double fire combines an `alert()` when `strategy.entry()` is called with an alert configured for both alert calls and order fills. The first message represents order creation logic; the second represents the later simulated fill. If both reach the same live-order endpoint, one strategy action can become two external attempts. Assign one trigger source per external intent and route diagnostic alerts somewhere that cannot place trades.

`close > ema` can be true on many consecutive bars, while `ta.crossover(close, ema)` identifies a transition. For complex state, track whether the strategy is already long, short, pending, or flat, and define an explicit reset. Alert frequency limits eligible emissions but cannot turn a poor condition into a correct state machine. TradingView also documents that more than fifteen alerts in three minutes causes further alerts to halt, so bursts can create both duplicate orders and missing later notifications.

Realtime bars contain fluid values. Once-per-bar-close reduces alerts that disappear from the historical chart after reload, but waiting for confirmation changes timing and may not fit every strategy. Document the choice. Then remember the server copy: TradingView captures a snapshot at alert creation. Version payload labels and keep an alert inventory so an old strategy does not continue routing after a visible chart update.

Pine does not provide a built-in JSON serializer. Every quote, backslash, comma, and conversion is the script author's responsibility. A long branch can work while a short branch omits a comma. A strategy label can include a quote. A calculation can become `na`. Test all directions, exits, minimum and maximum quantities, optional fields, and error branches. Copy a sanitized rendered body into a parser without including the endpoint token or credentials.

Types should be intentional. HexTrade's public examples quote several placeholder values and accept documented fields, but do not assume arbitrary coercion. Use one stable convention backed by current docs and dry-run tests. Avoid manually interpolating JSON around free-form user input. If the receiver returns 4xx for malformed data, TradingView's documented 5xx resubmission does not apply; syntax must be corrected and a new reviewed event created.

HexTrade's troubleshooting docs identify wrong platform slug, account mismatch, and ticker mismatch as common failures. Its symbol guide distinguishes futures roots such as NQ and MNQ from CFD names such as NAS100 and documents venue-specific mapping. Those strings can represent different products, not cosmetic aliases. Quantity, tick value, session, and margin must be reviewed whenever mapping changes the destination instrument.

Continuous futures charts add lifecycle risk. They support analysis across contracts but do not remove expiration from the broker route. Define who chooses the destination contract and when the mapping rolls. Because TradingView alerts retain a chart snapshot, updating the visible chart is not enough. Inventory active alerts, receiver mappings, working orders, and positions before a roll, then validate the new destination with dry mode and minimum live size.

Copying `sl: 20` from one market to another can produce a different price distance and money risk. Full-size and micro contracts also differ, so changing NQ to MNQ or ES to MES requires more than a string replacement. Write a worksheet with minimum tick, tick value, intended price distance, resulting tick count, quantity, and aggregate exposure. Align dynamic Pine calculations with the destination, not an unrelated chart context.

A `maxQty` guardrail catches a single oversized request but does not account for repeated webhooks, open positions, or copy-trading multipliers. `allowedSymbols` constrains instruments but not exposure. Protective fields express intent and may face broker support, rejection, market movement, or partial fills. Verify actual entry and protective orders in the destination account; a successful dry run proves only the planned request.

TradingView explicitly warns that alerts are not designed to carry credentials. Pine source, alert dialogs, screenshots, exports, and support messages can all expose body content. Use the private authenticated endpoint supplied by HexTrade and leave broker secrets in the platform's protected account connection. Redact the full URL in every artifact; knowing only that it is HTTPS does not make its embedded token public.

Retry myths create order risk. A malformed 4xx request is not automatically retried under the published rule, while a qualifying 5xx can create four total deliveries. A 504 is specifically excluded. A request cancelled after the three-second deadline may still have reached a receiver that continued work. Correlate repeated arrivals, make the execution path idempotent where supported, and reconcile unknown broker state before manual replay.