MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+1 888 340 6572 GET STARTED
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
bug_report_small.png
Open Bug report MC-562

Built-in Exit strategy "Stop Loss" does not work.

action_vote_minus_faded.png
3
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

When creating a stop order on the chart and attaching a "Stop Loss" exit strategy to it the expected behavior is that it should be activated after the initial stop order is filled.
This does not happen.
After initial order is hit the "Stop Loss" disappears from the chart.
Leaving the open position with no Stop Loss.

Steps to reproduce this issue
  1. Put in a stop order on the chart for EuroFX futures (6E) with Open E Cry as broker.
  2. Right click order => Attach Exit Strategy => Stop Loss
  3. Wait until stop order from point 1 above is filled.
  4. Stop Loss is gone.
Comments (1)
#0
user-offline.png  larssan (larssan)
Aug 26, 2011 - 11:04

I added a picture to show the issue.
Broker is OEC and symbol ZCZ1.
So far I have this issue with ZC, 6E, CL and NG.
Both Stop and Limit orders.
It does not happen every time but about 10% of the Stop Loss orders are disappearing.

History
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targeted for
    MultiCharts 7.1 (RELEASED)
  • Status
    Released
  • Priority
    Not determined
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
  • Reproducability
    Not determined
  • Severity
    Critical
Attachments (1)
  • /pm/public/files/show/235
    Bug produced with limit order when trading Corn uploaded Aug 26, 2011 by larssan (larssan)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates