+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-1497 » Open Feature request MC-1027

Don't cancel pending stop-loss orders with additional entry orders

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

In MC8 stop-loss orders are cancelled when an additional entry order is given. This works currently as following:

1) The position is opened with the entry order ('EL #1'),
2) A stop-loss is submitted for this entry order,
3) An additional entry ('EL #2') is triggered,
4) Now, the original stop-loss order for the first part of the position ('EL #1') is cancelled,
5) The cancelled stop-loss is immediately resubmitted (with same quantity and same price!) and a stop-loss order for the second entry is submitted.

This is problematic because of two reasons. First, the trader loses his position in the order queue with the needless cancellation of the original stop-loss order. Secondly, certain exchanges (like Eurex) charge cancellation fees. Since all open stop-loss orders are cancelled when an additional entry order is placed, these additional fees can quickly add up.

This behavior is confirmed by MC support since 'at the moment it is not possible to send the price order(limit/stop) simultaneously with a market one. Unfilled price orders are to be cancelled. If the number of sent price orders changes - unfilled price orders are to be cancelled.'

Suggestion: keep the pending stop-loss orders active when an additional entry is submitted.

Steps to reproduce this issue


Comments (1)
user-offline.png  MultiCharts Support (MultiCharts)
Oct 15, 2013 - 12:42
Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
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