Probably, the market markup is the answer. SymbolInfo comes from the market watch which is affected by the markup (depending from your account settings), thereas tick history contains raw ticks from broker's market source "as is" and can even be used in parallel for several types of accounts with different markups. Here is an excerpt from Russian forum (i'm not sure this thread is available in autotranslated English equivalent).
I often encounter situations where prices in the Market Watch don't correspond to the historical price due to the specified markup, depending on which account group you're in.
Probably, the market markup is the answer. SymbolInfo comes from the market watch which is affected by the markup (depending from your account settings), thereas tick history contains raw ticks from broker's market source "as is" and can even be used in parallel for several types of accounts with different markups. Here is an excerpt from Russian forum (i'm not sure this thread is available in autotranslated English equivalent).
Thank you, @Stanislav Korotky, for your explanation and the original Russian forum reference.
Your account-group pricing explanation looks relevant to my November 9 EURUSD observations.
I reviewed the referenced fxsaber discussion and the official SymbolInfoTick() and CopyTicksRange() documentation.
There is one specific detail I would appreciate your help understanding.
Both have time_msc = 1794248101878 and flags = 1030.
The midpoint is identical.
The live snapshot remained unchanged before and after the historical query.
The live spread is 0.4 pip narrower than the historical spread.
If historical ticks contain the broker's raw source prices and account-group markup is applied to Market Watch, I would normally expect a positive live markup to widen the spread.
Could you please clarify:
Can MT5 account-group pricing legitimately produce a narrower live Bid/Ask spread than the stored historical source?
Is there an official MetaQuotes document explaining whether historical tick data is stored before or after account-group pricing adjustments?
Is there a documented, read-only way to verify which pricing representation is returned, without accessing broker-admin settings or placing trades?
FOREX.com has confirmed that account-group spread configuration is under its control, but Client Support cannot confirm the actual demo configuration.
I am not proposing any price correction until the mechanism is verified.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Probably, the market markup is the answer. SymbolInfo comes from the market watch which is affected by the markup (depending from your account settings), thereas tick history contains raw ticks from broker's market source "as is" and can even be used in parallel for several types of accounts with different markups. Here is an excerpt from Russian forum (i'm not sure this thread is available in autotranslated English equivalent).
Forum on trading, automated trading systems, and trading strategy testing
New MetaTrader 5 platform version 2450: Subscriptions service, interface improvements, and usability improvements in MetaEditor
fxsaber , May 17, 2020, 12:38 AM
I often encounter situations where prices in the Market Watch don't correspond to the historical price due to the specified markup, depending on which account group you're in.
Probably, the market markup is the answer. SymbolInfo comes from the market watch which is affected by the markup (depending from your account settings), thereas tick history contains raw ticks from broker's market source "as is" and can even be used in parallel for several types of accounts with different markups. Here is an excerpt from Russian forum (i'm not sure this thread is available in autotranslated English equivalent).
Thank you, @Stanislav Korotky, for your explanation and the original Russian forum reference.
Your account-group pricing explanation looks relevant to my November 9 EURUSD observations.
I reviewed the referenced fxsaber discussion and the official SymbolInfoTick() and CopyTicksRange() documentation.
There is one specific detail I would appreciate your help understanding.
In my preserved native MQL5 evidence:
SymbolInfoTick(): Bid 1.12025, Ask 1.12040, spread 1.5 pips
CopyTicksRange(): Bid 1.12023, Ask 1.12042, spread 1.9 pips
Both have time_msc = 1794248101878 and flags = 1030.
The midpoint is identical.
The live snapshot remained unchanged before and after the historical query.
The live spread is 0.4 pip narrower than the historical spread.
If historical ticks contain the broker's raw source prices and account-group markup is applied to Market Watch, I would normally expect a positive live markup to widen the spread.
Could you please clarify:
Can MT5 account-group pricing legitimately produce a narrower live Bid/Ask spread than the stored historical source?
Is there an official MetaQuotes document explaining whether historical tick data is stored before or after account-group pricing adjustments?
Is there a documented, read-only way to verify which pricing representation is returned, without accessing broker-admin settings or placing trades?
FOREX.com has confirmed that account-group spread configuration is under its control, but Client Support cannot confirm the actual demo configuration.
I am not proposing any price correction until the mechanism is verified.
Thank you for your valuable technical guidance. @Stanislav Korotky