NRUNO Trading Automation Wiki · Question 82

How should partial closes be represented in webhook commands?

Webhooks, Delivery & ReliabilityLast reviewed: 25 Aug 2026
Short answer

A partial-close command should identify the target position/strategy scope and an explicit quantity or percentage to close. Do not use an ambiguous SELL command when the intent is to reduce a long.

What this means in practice

A partial-close command should identify the target position/strategy scope and an explicit quantity or percentage to close. Do not use an ambiguous SELL command when the intent is to reduce a long. This page is specifically about “How should partial closes be represented in webhook commands?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Close 50%

Use actual current position volume as the source of truth. A partial close must specify which position to reduce and by how much; later risk and protection should use the remaining cTrader volume. For Scenario A — Close 50% on question 82, use that evidence specifically to answer “How should partial closes be represented in webhook commands?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Close fixed units

Compare requested size with the cTrader symbol minimum, maximum and step. Convert to one canonical internal unit, normalize once, and log requested versus submitted volume. For Scenario B — Close fixed units on question 82, use that evidence specifically to answer “How should partial closes be represented in webhook commands?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Several hedged positions

Resolve current cTrader exposure before acting. An opposite order can hedge, flatten or reverse depending on account model and state, so explicit OPEN, CLOSE and REVERSE semantics are safer than ambiguous BUY/SELL behavior. For Scenario C — Several hedged positions on question 82, use that evidence specifically to answer “How should partial closes be represented in webhook commands?”; 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 partial closes be represented in webhook commands?”, 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: A partial-close command should identify the target position/strategy scope and an explicit quantity or percentage to close. Do not use an ambiguous SELL command when the intent is to reduce a long.

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.