Thank you for your response.
The java class AnalyticsPluginInstance evaluates/indicates that the chosen timezone defined in Automation Engine objects is proper or not..
In case TZ name is different than Supported Timezones abbreviation: CET (UTC+02:00), MET (UTC+02:00), GB (UTC+01:00), PST8PDT (UTC-07:00), MST7MDT (UTC-06:00), CST6CDT (UTC-05:00), EST5EDT (UTC-04:00), ROK (UTC+09:00), PRC (UTC+08:00), W-SU (UTC+03:00), WET (UTC+01:00), GMT (UTC+00:00), NZ (UTC+13:00), NZ-CHAT (UTC+13:45) then the analytics uses the default timezone UTC (-3 hours than mine).
So now the timezone name is defined with the proper CET but from the other hand the issue there is -1 hour difference in analytics, obviously because the Daylight Saving Time now is utc+3 (summertime) while the default value for the CET object timezone is utc+2.
If i change CET object from utc+2 to utc+3, the report is 1 hour in advance.
I guess the Daylight Saving Time can't be recognized in analytics, it keeps the default utc+2 timezone value. Is that true?
Does anyone solve this issue somehow?