+1 888 340 6572 GET STARTED

Open Bug report MC-2376

xxx Bars Back Setting for Data Range loads appr. 3 months of data only

Votes

- No additional actions available

Description

When selecting xxx Bars Back option in Instrument settings for a chart or in PT, MC loads only appr. 3 months of data.

Steps to reproduce this issue

Create Chart
Select an instrument e.g. EUR.USD with 60min resolution.
Select an option with "....Bars Back" from current and input a high number - e.g. 10000
See data loaded and chart created
Look at the beginning of the chart and see that the date is appr. 3 months ago only...regardless of the resolution chosen (60min or 240 min).

Comments (1)

Toggle system-generated comments

MultiCharts Support (MultiCharts)

MultiCharts Support
Last seen online at Apr 17, 2024 - 12:37
Show user details

Nov 10, 2017 - 22:10

Hello Zheka,

That is expected behavior. When using “Bars Back” request on intra-day resolutions - the history will never exceed 91 days, even if you have more data in the database. The limitation is applied to avoid overloading the data providers with requests that cannot return data (infinitely going back to 1900 for ex.). In order to load the desired data range – please use the "Days Back" or "From-To" request types.

Changes:

Status changed: Under Review => Not a bug

Reply to comment #1

Comment visibility (whether to hide this comment for "regular users")

Selected syntax: Mediawiki ▼

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

Code samples are best presented between two "~~~~"-lines. The Bug Genie uses GeSHi for syntax highlighting with support for over 100 languages! (<source lang="php"><?php echo "fu"; ?></source>)
See more formatting tips in MarkdownFormatting.

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples in tags.
See more formatting tips in WikiFormatting.

or cancel

History

Issue basics

Type of issue

Bug report Unknown issue type
Issue label

No label set
Category

Not determined
Targeted for

Not determined
Status

Not a bug

Status not determined
Progress
Priority

Not determined

Affected by this issue (0)

There are no items

People involved

Posted by
Zheka (Zheka)

Evgeni Andreyev
Last seen online at Apr 04, 2024 - 11:55

Show user details
Owned by

Not owned by anyone
Assigned to

Not assigned to anyone
Subscribers

2 subscriber(s)

Click here to show the list of subscribers

Times and dates

Posted at

Nov 07, 2017
Last updated

Nov 10, 2017
Estimated time

Not estimated
Time spent

No time spent

Click here to see time logged against this issue

Issue details

Resolution

Not determined
Reproducability

Not determined
Severity

Not determined

Attachments (0)

There is nothing attached to this issue

Commits (0)

There are no code checkins for this issue

Child issues (0)

This issue does not have any child issues

Duplicate issues (0)

This issue does not have any duplicates