A schedule set for «3 AM» runs at 3 AM somewhere — just not necessarily where you are sitting when you set it, because the node keeps its own clock, entirely independent of the browser session used to configure the task.
Why it happens
Scheduled tasks are evaluated against the node's own system clock, not the timezone your browser reports or the local time you were thinking in when you typed the hour. A task created without accounting for that runs at the correct hour on the wrong clock — which is why a backup «at 3 AM» can quietly fire in the middle of a busy evening for players in a different timezone from the node.
What to do
- Find the node's current time
The panel or a world clock for the node's location gives you the reference point everything else is calculated from.
- Work out the offset to your own local time
A fixed number of hours, adjusted once for daylight saving if the node observes it.
- Enter the schedule in the node's time, not yours
The field takes node time regardless of what timezone you are physically in when you fill it out.
The task's next-run time shown in the panel matches when you actually expect it to fire, once converted to your own timezone.