+1 888 340 6572 GET STARTED
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-1421

Unexpected flush of history orders as realtime orders when connection was reestablished

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

MC 8.7 added a feature to backfill automatically missing data when broken internet connection is reestablished. This is a very good feature. However, there is a serious issue regarding automatic trading.
MC 8.7 treats the backfilled history data as realtime data and as a result, all the history orders for that backfilled data are generated as realtime ones. This is can be a feature to some people but it is a disaster to others who don't want to place old history orders with old prices (that are not valid for trading any more) as realtime orders.

I experience huge number of wrong and unexpected history orders get flushed when internet connection was restored and was so surprised to cancel all the backfilled history orders manually. It was a night mare. There is no other way to downgrade to 8.0.
It's like that I used MC 10 days ago and had a trip. After I come back, I opened it again and all of a sudden I got all the last 10 days orders got flushed to my real trading account. This is not acceptable for me and I am sure many others would agree with this.

So please backfill the missing data as of now, but DON'T place history orders as realtime ones. Or, at least I would like to have an option to disable flushing of history orders as realtime ones. I think 'disable' for this option should be the default.

Please resolve this issue ASAP.

Thank you

Steps to reproduce this issue

I've reported this issue and engineers and help desk faculties already know this issue.
I was asked to post this issue in this PM.

Comments (0)
Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    MultiCharts 9.0 (RELEASED)
  • Status
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
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