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

Order Cancellation

action_vote_minus_faded.png
7
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

Suppose we have a 60 min bar chart. it's known on each bar close we have the ability to generate new orders, and if we are in automated trading, this order are sent to our broker. Suppose that our system wants to take a market posistion only between 10:00 a.m. and 20:00 p.m. even if the market can be traded between 00:00 a.m. and 23:00 p.m. Well, in this scenario you write

if 1000 < time and time < 2000 then buy next bar StopValue stop;

The problem is that after 20:00 the previous stop order should be removed from the broker to prevent any filling after the specified time.

Now that's not possible and while on the chart nothing is filled, the same could not happen on the broker side. You understand that is not acceptable.

We need a ClearAllPending keyword.

Steps to reproduce this issue

You can try it on a Demo IB Account. Try to write in your PLEditor

if time < AnyTime then buy next bar SomeValue stop;

Make sure the order have a low probability to be filled, i.e. choose a stop price large, and afetr AnyTime is past look to pending orders at the broker side. They still there.

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • 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
    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