ElasticJob lacks time zone support for cron schedules, causing incorrect trigger times

ElasticJob lacks time zone support for cron schedules, causing incorrect trigger times: a task in LegoFlow-SWE (Harbor dataset). ElasticJob scheduling does not currently allow users to associate a time zone with a cron-based job. All cron expressions are evaluated in the server’s default time…

The task

ElasticJob scheduling does not currently allow users to associate a time zone with a cron-based job. All cron expressions are evaluated in the server’s default time zone, which breaks deployments that require a fixed region schedule (for example, US/Eastern) and causes mis-aligned firing during daylight saving time…

Part of Lego-X/LegoFlow-SWE.