i didnt get it work.

I tested an expert with Candle Color and it works fine.

Please upload your expert for further analysis. It can be another reason and we must find and fix it.

any idea about that?

This bug can happen when you start the backtest at the exact beginning of a historical data, and for some strategies requires an index that go outside the array size (for these Time[], Open[], High[], Low[], Close[]).
I solved and fixed this bug by modyfing the code like that:

datetime Time(int bar){ if(bar >= ArraySize(Time)) return 0; return Time[bar];}
double Open(int bar){   if(bar >= ArraySize(Open)) return 0; return Open[bar];}
double High(int bar){    if(bar >= ArraySize(High))  return 0; return High[bar];}
double Low(int bar){     if(bar >= ArraySize(Low))   return 0; return Low[bar];}
double Close(int bar){   if(bar >= ArraySize(Close)) return 0; return Close[bar];}

@Popov I thinnk you can modify this code in the current MQL template, in order to fix this bug with that solution.

Yes, it's possible to start the backtest from the first bar (when you download data from Tickstory for example or other third-party providers), in this case when the backtest starts at the beginning of downloaded datas, it doesn't show any previous bar and therefore the size of these standard arrays (Time[], Open[], etc...) are limited to the actual bars.
With some strategies, that uses these values, this can happen.

@Popov here a screenshot where I made a Print of the value of the ArraySize of Time and it shows also the number of Bars on the chart (that of course are equal to ArraySize(Time).

The purpose of importing data into MT4 is to make high quality backtests from tick by tick data; MT4 by default uses the global history data that are not good for tick by tick backtests, instead Tickstory or Tickdata Suite are optimal choices for professional backtest and these data are taken from Dukascopy database (@Popov the same provider that you are using for Premium Data on EA Studio).

It's possible to overcome these "Array out of range" problems by starting the backtest 1 or 2 days later, but @Popov you know that "Array out of range" is not a problem from a backtest but from a source code and needs to be managed properly.

Like I told you, a possible solution is to put a simple condition before accessing to the actual array, like that:

datetime Time(int bar){
    if(bar >= ArraySize(Time)) return 0;
    return Time[bar];
}

instead of

datetime Time(int bar){
    return Time[bar];
}

Think about that, maybe for the next release.
Thank you @Popov

yes, it's a solution

@Popov, you forgot to define the macro REQUIRED_BARS, in fact it doesn't compile because of this error (both on MQL for single EA and Portfolio)