What is pyramiding and how can it accidentally create multiple positions?

What this means in practice

Pyramiding controls successive strategy.entry() additions in the same direction. If each resulting alert becomes a fresh live entry, intentional or accidental pyramiding can multiply cTrader exposure. This page is specifically about “What is pyramiding and how can it accidentally create multiple positions?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Scale-in

Decide whether extra entries are intentional scale-ins or accidental duplicates. Give each intended scale-in its own identity and keep TradingView pyramiding separate from transport or cBot duplicate protection. For Scenario A — Scale-in on question 81, use that evidence specifically to answer “What is pyramiding and how can it accidentally create multiple positions?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Pyramiding misunderstood

Decide whether extra entries are intentional scale-ins or accidental duplicates. Give each intended scale-in its own identity and keep TradingView pyramiding separate from transport or cBot duplicate protection. For Scenario B — Pyramiding misunderstood on question 81, use that evidence specifically to answer “What is pyramiding and how can it accidentally create multiple positions?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Duplicate execution

Inspect the mechanism named by “Scenario C — Duplicate execution” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Duplicate execution on question 81, use that evidence specifically to answer “What is pyramiding and how can it accidentally create multiple positions?”; keep it separate from the evidence for the other scenarios on this page.

What to check

• target connector/account identity
• exact broker symbol
• normalized order parameters
• cTrader response and final position/order state

Practical rule

For “What is pyramiding and how can it accidentally create multiple positions?”, 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.