DBMS_SCHEDULER and DST

Database Release 18.0.0.0.0 Version 18.3.0.0.0 - OS Microsoft Windows 10 64bit

Last night in Central Europe we moved from CEST to CET (one hour back according to current DST rules). While 'the rest of the database' is obviously aware of that change, the Scheduler is not.

I query 'select WINDOW_NEXT_TIME from DBA_AUTOTASK_WINDOW_CLIENTS;' and (for example) the output for Monday is:

29.10.18 07:00:00,000000 +02:00 <==  that's still UTC + 2 Hours , i.e. CEST

My question: is this behaviour a bug or does it work as expected?

I can remedy the problem, I only need to execute ' exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('default_timezone','');'  and all is fine.