We have fixed that issue in the 4.1 Composer released the issues that fixed had this descrition:
Scheduler does not take into account timezone. So if the user wants to run schedule job on a specific time, it will run correctly only if server and user browser are in one timezone. Let go through this case:
time now for user is 18:00
time now on server is 16:00
the user creates schedule and wants it to be run on 22:00
Actual: job will run on 22:00 (server time). For user it will be midnight
Expected: job should be run on 22:00 for user (20:00 server time)
fixed in the 4.1 please contact your account manager for details on the upgrade.