# Script schedules run in UTC while Automatic updates use the server timezone (not shown in the UI)

**Project:** Bugs | **Votes:** 2
**URL:** https://roadmap.ploi.io/projects/7-bugs/items/1632-script-schedules-run-in-utc-while-automatic-updates-use-the-server-timezone-not-shown-in-the-ui

---

Automatic updates and script schedules seem to use different timezones, and the UI doesn't say which one applies.

Setup: 10 servers, server timezone Europe/Amsterdam (timedatectl: CEST, +0200).

Steps to reproduce:
1. Set Automatic updates to Daily, 02:00 on a server.
2. On a script, click Schedule and add the cron expression `30 3 * * *` for the same server.
3. Let the script write the output of date to a log file.

Expected: both schedules use the same timezone (the server timezone), or the UI clearly shows which timezone applies.

Additional observation: the "Next run" shown on a script's schedule is converted to my local browser time, while the scheduler itself evaluates the cron expression in UTC.

Example (Europe/Amsterdam, DST ends on 2026-10-25): I set the schedule `0 10 * * *` and the UI shows "Next run: 10/25/2026, 11:00:00 AM". That matches 10:00 UTC converted to CET (UTC+1). It doesn't say anywhere that the expression is in UTC, so it's easy to read the displayed time as server time or as the time I typed in.

Also unexpected: it was 09:50 UTC when I set it, so I expected the first run today at 10:00 UTC, but the UI shows tomorrow.

Suggestion: show the timezone next to the cron field and next to "Next run" (for example "10:00 UTC / 11:00 Europe/Amsterdam").

Related: https://roadmap.ploi.io/projects/4-ploi-core-requests/items/1633-script-trigger-after-automatic-updates-to-restart-pm2-reload-services-or-reboot (I use a cron schedule, because Ploi lacks a trigger for scripts to run after automatic updates have run)