+1 888 340 6572
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-1057

Keep OCO Stop orders at broker when MC is closed

Go to the next issue (open or closed)
Go to the next open issue

Currently, OCO orders not handled by the broker are simulated by MC. When MC is closed before one is flat on an open position with attached OCO orders the OCO orders are canceled before MC is terminated. Unfortunately, if one only uses a stop order and not a profit target that stop order is also canceled before MC terminates though that is not necessary. In that case MC does not need to simulate anything, and of course it would make sense to keep the stop order alive: 1) A possible loss is still limited, 2) If one was already in profit and adjusted the stop such that profits were already locked they keep locked after MC terminated.
If a trader uses only one part of an OCO group, please keep that order at the broker even after MC terminated.

Steps to reproduce this issue

Use Multicharts 8.0.5622.401 x64 on Microsoft Windows 7 Professional x64. Open a position with active stop order and terminate MC. Reopen MC and the stop order is no longer alive.

Comments (3)
user-offline.png  MultiCharts Support (MultiCharts)
May 22, 2013 - 10:56

Manual Stop Loss is not cancelled any longer

user-offline.png  bltoby (bltoby)
Jan 15, 2014 - 07:50

still not implemented. although some APIs have supported native OCO orders at server side. (CQG Rithmic e.g.)

user-offline.png  MultiCharts Support (MultiCharts)
Jan 15, 2014 - 10:34

Rithmic API allows only 1 stop and 1 profit target OCO orders as far as we know. This is not complete OCO group support, since more orders can be sent as OCO, that's why emulation is used locally in MC.

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    MultiCharts 8.5 (RELEASED)
  • Status
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates