+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-838

Checking the validity of the input when using Exit Strategy orders
action_vote_minus_faded.png
1
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

Currently, on a Short order, you can attach an Exit Strategy including a Stop Loss price which is less than the entry price and a Take Profit price which is higher than the entry price.
You can validate such a setting.
No consistency check is performed by MultiCharts.
The problem will take place upon the execution of your entry order, MultiCharts detect at this time inconsistency and will close your order instantly.
One solution (used on the Oanda platform) would be to test at the time of validation of the Exit Strategy order and to refuse this validation by displaying an error message "Stop Loss must be above quote (xxx,xxx), where xxx is the entry price.

Steps to reproduce this issue

Place a Long order.
Attach for example an Exit Bracket Strategy
Set the stop loss at a price which is above the entry price.
Validate.
Wait until your entry price is reached.
See what happened : your entry order has been executed, and your order was immediately closed with an error message in the logs of the Order and Position Tracker.

Comments (0)
icon-mono-settings.png
History
sidebar_collapse.png sidebar_expand.png
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Under Review
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
    Normal
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