Skip to content

Configured time zone ignored for scheduled tasks. #1416

@k-elle

Description

@k-elle

Operating System

Windows 10 Pro 22H2

AMP Version and Build Date

2.7 - 20260308.1

AMP Release Stream

Mainline

I confirm that

  • I have searched for an existing bug report for this issue.
  • I am using the latest available version of AMP.
  • my operating system is up-to-date.

Intended Action

Create a scheduled task in my time zone. Specifically, I wanted to create a task to run at 3:55am AEST (UTC+10:00).

Expected Behaviour

The scheduled task would run at the correct time in local time - 3:55am AEST.

Actual Behaviour

The scheduled task runs at the correct time, but in the UTC time zone. It runs at 1:55pm AEST, which is 3:55am UTC,

Reproduction

In the main menu, open Configuration > System Settings, then click the System tab. Set "Scheduler Timezone" to "(UTC+10:00) Brisbane". Go back to the main menu.

Create a Minecraft instance, and manage the instance once setup. In the instance management, open Configuration > System Settings, then click the System tab. Set "Scheduler Timezone" to "(UTC+10:00) Brisbane".

Go back to instance management, and open Schedule. Click "Add New Trigger", then "Simple Time Interval". Set trigger interval (Once per day), at 03:55. Note the text in this window says "Server Timezone: E. Australia Standard Time". Click "Add New Trigger".

Click "Add New Task", and add a task (my specific setup added a message, then a wait for 300 seconds task, then a "Backups - Shut the server down, take a backup, and start it up again." task.

Wait for the trigger - the tasks all happen correctly, but at 3:55am UTC rather than 3:55am AEST.

Image Image Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions