This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Price not Reached' count can be used for example to keep a count of how many stop or limit orders were cancelled by the EA before the required execution price was reached, or when a TOP (Target Opening Price) was not reached before the potential trade was timed out.

If this value is too high, it provides valuable insights to the trader about either too short an expiry time being used, or that the target price might be being set too far away from the current price.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__TARGET_OPEN_PRICE_NOT_REACHED)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Risk too High' metric can be used for example to keep a count of the number of times the Expert Advisor did not allow trades to be opened (even though an open signal was generated) because the EA determined that the risk would have been too great on the account/portfolio even if using the broker's minimum lot size.

If this value is high, it might suggest that the position sizing model being used is not aggressive enough (not willing to accept a high enough risk), but if for example the EA is using some form of Correlation Management assessment, it would then be usual for this value to be high and simply illustrates how the strategy inhibits trades when they are too correlated to existing positions in the portfolio.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__RISK_TOO_HIGH)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Insufficient Margin' metric can be used for example to keep a count of the number of times trades could not opened because MT5 idicated there was insufficient margin to allow them (TRADE_RETCODE_NO_MONEY returned by OrderSend()).

If this metric is too high it suggests a position sizing model that is too aggressive / too high risk. It is recommended that you investigate the margin profile shown on the equity chart and reduce position sizing until you consider the margin usage is at an acceptable level that doesn't expose the account to too much risk.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__INSUFFICIENT_MARGIN)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Excessive Spread' metric can be used for example to keep a count of the number of times trades could not opened because the Expert Advisor determined that the spread of the asset was larger than the max allowed spread at the time the open signal was generated (e.g. if a trade open signal was generated outside of normal trading hours).

For experts that do monitor spread before allowing a trade to open, a value > 0 here is completely normal and expected, however, if this metric is too high it suggests the 'Maximum Allowed Spread' being used by the EA is too strict for one or more assets and might be preventing trades from opening during normal hours.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__EXCESSIVE_SPREAD)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Price not Reached' count can be used for example to keep a count of how many stop or limit orders were cancelled by the EA before the required execution price was reached, or when a TOP (Target Opening Price) was not reached before the potential trade was timed out.

If this value is too high, it provides valuable insights to the trader about either too short an expiry time being used, or that the target price might be being set too far away from the current price.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__TARGET_OPEN_PRICE_NOT_REACHED)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Risk too High' metric can be used for example to keep a count of the number of times the Expert Advisor did not allow trades to be opened (even though an open signal was generated) because the EA determined that the risk would have been too great on the account/portfolio even if using the broker's minimum lot size.

If this value is high, it might suggest that the position sizing model being used is not aggressive enough (not willing to accept a high enough risk), but if for example the EA is using some form of Correlation Management assessment, it would then be usual for this value to be high and simply illustrates how the strategy inhibits trades when they are too correlated to existing positions in the portfolio.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__RISK_TOO_HIGH)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Insufficient Margin' metric can be used for example to keep a count of the number of times trades could not opened because MT5 idicated there was insufficient margin to allow them (TRADE_RETCODE_NO_MONEY returned by OrderSend()).

If this metric is too high it suggests a position sizing model that is too aggressive / too high risk. It is recommended that you investigate the margin profile shown on the equity chart and reduce position sizing until you consider the margin usage is at an acceptable level that doesn't expose the account to too much risk.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__INSUFFICIENT_MARGIN)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Excessive Spread' metric can be used for example to keep a count of the number of times trades could not opened because the Expert Advisor determined that the spread of the asset was larger than the max allowed spread at the time the open signal was generated (e.g. if a trade open signal was generated outside of normal trading hours).

For experts that do monitor spread before allowing a trade to open, a value > 0 here is completely normal and expected, however, if this metric is too high it suggests the 'Maximum Allowed Spread' being used by the EA is too strict for one or more assets and might be preventing trades from opening during normal hours.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__EXCESSIVE_SPREAD)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Price not Reached' count can be used for example to keep a count of how many stop or limit orders were cancelled by the EA before the required execution price was reached, or when a TOP (Target Opening Price) was not reached before the potential trade was timed out.

If this value is too high, it provides valuable insights to the trader about either too short an expiry time being used, or that the target price might be being set too far away from the current price.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__TARGET_OPEN_PRICE_NOT_REACHED)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Risk too High' metric can be used for example to keep a count of the number of times the Expert Advisor did not allow trades to be opened (even though an open signal was generated) because the EA determined that the risk would have been too great on the account/portfolio even if using the broker's minimum lot size.

If this value is high, it might suggest that the position sizing model being used is not aggressive enough (not willing to accept a high enough risk), but if for example the EA is using some form of Correlation Management assessment, it would then be usual for this value to be high and simply illustrates how the strategy inhibits trades when they are too correlated to existing positions in the portfolio.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__RISK_TOO_HIGH)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Insufficient Margin' metric can be used for example to keep a count of the number of times trades could not opened because MT5 idicated there was insufficient margin to allow them (TRADE_RETCODE_NO_MONEY returned by OrderSend()).

If this metric is too high it suggests a position sizing model that is too aggressive / too high risk. It is recommended that you investigate the margin profile shown on the equity chart and reduce position sizing until you consider the margin usage is at an acceptable level that doesn't expose the account to too much risk.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__INSUFFICIENT_MARGIN)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Excessive Spread' metric can be used for example to keep a count of the number of times trades could not opened because the Expert Advisor determined that the spread of the asset was larger than the max allowed spread at the time the open signal was generated (e.g. if a trade open signal was generated outside of normal trading hours).

For experts that do monitor spread before allowing a trade to open, a value > 0 here is completely normal and expected, however, if this metric is too high it suggests the 'Maximum Allowed Spread' being used by the EA is too strict for one or more assets and might be preventing trades from opening during normal hours.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__EXCESSIVE_SPREAD)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Price not Reached' count can be used for example to keep a count of how many stop or limit orders were cancelled by the EA before the required execution price was reached, or when a TOP (Target Opening Price) was not reached before the potential trade was timed out.

If this value is too high, it provides valuable insights to the trader about either too short an expiry time being used, or that the target price might be being set too far away from the current price.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__TARGET_OPEN_PRICE_NOT_REACHED)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Risk too High' metric can be used for example to keep a count of the number of times the Expert Advisor did not allow trades to be opened (even though an open signal was generated) because the EA determined that the risk would have been too great on the account/portfolio even if using the broker's minimum lot size.

If this value is high, it might suggest that the position sizing model being used is not aggressive enough (not willing to accept a high enough risk), but if for example the EA is using some form of Correlation Management assessment, it would then be usual for this value to be high and simply illustrates how the strategy inhibits trades when they are too correlated to existing positions in the portfolio.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__RISK_TOO_HIGH)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Insufficient Margin' metric can be used for example to keep a count of the number of times trades could not opened because MT5 idicated there was insufficient margin to allow them (TRADE_RETCODE_NO_MONEY returned by OrderSend()).

If this metric is too high it suggests a position sizing model that is too aggressive / too high risk. It is recommended that you investigate the margin profile shown on the equity chart and reduce position sizing until you consider the margin usage is at an acceptable level that doesn't expose the account to too much risk.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__INSUFFICIENT_MARGIN)

See documentation for further details.

This value will always be 0 by default since further optional configuration is required in the Expert Advisor to pass this information through to OMS (if the user would find this information useful for their own analysis purposes).

The 'Excessive Spread' metric can be used for example to keep a count of the number of times trades could not opened because the Expert Advisor determined that the spread of the asset was larger than the max allowed spread at the time the open signal was generated (e.g. if a trade open signal was generated outside of normal trading hours).

For experts that do monitor spread before allowing a trade to open, a value > 0 here is completely normal and expected, however, if this metric is too high it suggests the 'Maximum Allowed Spread' being used by the EA is too strict for one or more assets and might be preventing trades from opening during normal hours.

The logic to enable this would need to be built into the expert advisor by the user and the count can then be incremented in OMS by calling the following from the EA:

TLAM_OMS_IncrementNonOpeningCount(OMS_NON_OPENING_REASON__EXCESSIVE_SPREAD)

See documentation for further details.