When AutoSys is running in any timezone other than UTC, and is using Azure SQL DB for the Event Server, jobs run at the wrong time. The time they run equals the difference in Scheduler time and UTC.
The Scheduler and the Event Server must run in the same timezone for jobs to schedule properly.
Azure SQL DB only runs in UTC and does not support other timezone settings.
Azure SQL MI can be set to a different timezone, but it has to be done when the managed instance is created. It cannot be changed without setting up a new managed instance.
If using Azure SQL DB, your scheduler must also run in UTC. Job schedules must be set accordingly. Their start times must reflect UTC, or they must use a timezone attribute.
If using Azure SQL MI, make sure to set the timezone for the managed instance to that which the Scheduler will be running.