NRUNO Trading Automation Wiki · Question 43

How do I fix cTrader BadVolume errors?

cTrader Execution & Broker ErrorsLast reviewed: 25 Aug 2026
Short answer

BadVolume means the requested volume is invalid. Check the symbol minimum, maximum and step, convert lots to units correctly, and normalize calculated volume before submission.

What this means in practice

BadVolume means the requested volume is invalid. Check the symbol minimum, maximum and step, convert lots to units correctly, and normalize calculated volume before submission. This page is specifically about “How do I fix cTrader BadVolume errors?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Below minimum

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 A — Below minimum on question 43, use that evidence specifically to answer “How do I fix cTrader BadVolume errors?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Wrong lots-to-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 — Wrong lots-to-units on question 43, use that evidence specifically to answer “How do I fix cTrader BadVolume errors?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Not aligned to step

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 C — Not aligned to step on question 43, use that evidence specifically to answer “How do I fix cTrader BadVolume errors?”; keep it separate from the evidence for the other scenarios on this page.

Scenario D — Above maximum

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 D — Above maximum on question 43, use that evidence specifically to answer “How do I fix cTrader BadVolume errors?”; keep it separate from the evidence for the other scenarios on this page.

What to check

  • symbol metadata and unit conversion
  • configured risk or management rule
  • broker min/max/step or distance constraint
  • normalized value actually sent to cTrader

Practical rule

For “How do I fix cTrader BadVolume errors?”, 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: BadVolume means the requested volume is invalid. Check the symbol minimum, maximum and step, convert lots to units correctly, and normalize calculated volume before submission.

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.