+1 888 340 6572
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-2590

Use IQFeed Symbol Refresh on Rolling Futures Contracts

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

I've posted this topic in the discussion forum, re-posting the issue here as a feature request.

Your text to link here...

During a futures contract roll, the IQFeed symbol database refresh happens overnight, as they have millions of symbol updates to do and that is the only practical way to do it. This takes a period of hours, and during this time the symbol shown in an MC chart is the old symbol, while the data shown in an MC chart is the new data. This can be confusing to a trader that is executing trades during this period. If I do a symbol search in MC during this symbol updating process, it will still show the old contract, even tho the data in the chart is the new contract. This is only an issue for a matter of hours, and by the next morning the symbol database, symbol in the chart, and the data are correct and match.

It is possible to use a symbol refresh that IQFeed sends with the new contract data, and show the symbol for the new contract immediately, along with the new contract data. MC currently retrieves the symbol from the symbol database, and while the database is being refreshed, MC will pull and display the old symbol. I would suggest that MC be modified to use the new symbol that is sent immediately with the new data, rather than pulling from the symbol database.

Thanks for considering my request.

Comments (0)
There are no comments
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 (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
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