MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+1 888 340 6572
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
feature_request_small.png
Open Feature request MC-1981

Risk of unlimited loss with stop-order when connection fails

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

I would like to attach a stoploss to my stop-order at the broker (LMAX), so I am safe in case Multicharts crashes or its connection gets lost.
The LMAX API supports stoploss for stop-orders:
public StopOrderSpecification(string instructionId, long instrumentId, decimal stopPrice, decimal quantity, TimeInForce timeInForce, decimal? stopLossPriceOffset, decimal? stopProfitPriceOffset);
So it would be great if the MC.Net API could expose this parameter as well.
This is currently blocking for my signal to go live with MC.
See also:

http://www.multicharts.com/discussion/viewtopic.php?f=19&t=49261&p=118897#p118897

Steps to reproduce this issue

1) My signal places a buy-stop-order, including GenerateStopLossPt(10).
2) I unplugged the network so MC loses internet connection.
3) The price hits the stop-order at the broker so the order is filled.
4) Result: there is no stoploss, since the internet connection from MC to broker is lost.

Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Not Reviewed
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
    Critical
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