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

Alerting user that some bars were missed during the backfill/ historical data request

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
Problem:
- if some data is missed during a backfill ( problem with broker API, no quotes, bars filtered out, etc), a user has no way of knowing.

Suggestion:
Upon backfill, MC/ PortfolioTrader should transparently "Alert" the user in case some data are missing.
These alerts should show a user the problematic symbols and - ideally - the time periods missed, so that it helps further investigation/decision-making ( whether to continue with trading or not).
Missed number of bars can be put (in red) next to the symbol, the detailed report about time periods missed should be exported to a file that will be opened if a user clicks on the "alert" message.
So, it can be 1 "big fat" alert message.

This should work when backfilling data, regardless of the method ("bars or intervals back", "to-from"), in MC and PT, both for minute and daily resolutions.

The challenge will be taking into account holidays/early closes - so as to reduce the number of "false positives".
Comments (0)
There are no comments
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 (1)
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