Market Close Error MT5 Backtesting Solved

[Mani13]

Hello Everyone,
I was struggling for may days when MT5 backtesting sudden stops working due to market close error.
First I thought it was metatrader software issue but few days later while searching here on forum I found that it is problem of Fxdreema platform,
Then I atleast get some topics where few users said to use time filter before each Buy/Sell block but when I used that way it doesn't make any effect.
But later I thought the issue is related to closing of trades so I used it before Close Position block and set time as in below picture, And the problem fixed.

[roar]

This problem is also mentioned here
https://fxdreema.com/forum/topic/16638/mt5-optimizer-not-working-with-many-fx-dreema-ea-resolved

and here
https://fxdreema.com/forum/topic/16494/close-positions-when-market-is-closed

I think it needs addressing @fxDreema

[Mani13]

@roar Thanks for sharing this way too described in first link, but I do not have much knowledge of coding to create such thing.

I have also tried the way second link is describing but that not worked for me as I am facing issue on multicurrency trade with grid as it close all positions which I don't want to close.

By the way these might help me in furture, Thank You for sharing.

[ambrogio]

@forexbob-0 I always use the time filter with the times allowed by the broker, as outside those times, both in backtest and in real time, no order will be closed or opened. Using purple blocks limits the recurrence of the error but does not trigger out-of-hours orders since the "market closed" error appears immediately on the first attempt to open or close orders outside the broker worktime.

[Mani13]

@roar I want to learn to make custom block,
Can you help me if we take example of code mentioned in above first link
I have copied that in the given area but don't know what to put in other spaces.

[Mani13]

Do, any expert help to complete this custom block,
As the previous solution now stops working suddenly, Few of the backtests goes fine but it showing error as in beginning