Schedules cron timing - server time vs local time #4891

Hi @eurlexa! I'm Dosu and I'm helping the Dokploy team.

The cron expression in Dokploy runs in the timezone configured for that schedule, which defaults to UTC if you haven't explicitly set one [1]. So with a cron of 15 4 * * * and no timezone override, the job fires at 04:15 UTC.

The Server Time badge in the UI shows your server's local timezone (determined via Intl.DateTimeFormat on the server), not necessarily UTC [2]. In your case it appears the server is reporting UTC (5:00 when your local CET is 7:00), which is consistent.

The timestamps shown next to already-run schedules are displayed in your browser's local time — that's standard browser behavior when rendering Date objects. That's why you see 6:15 (CET = UTC+2 in summer) for a job that ran at 04:15 UTC.

So to summarize your example:

• Cron 15 4 * * * → executes at 04:15 UTC (the schedule's configured timezone, defaulting to UTC)
• Server Time badge → shows 05:00 UTC (server's own timezone)
• Timestamp in UI → shows 06:15 CET (your browser converts the UTC timestamp to your local time)

You can set a specific timezone per schedule when creating or editing it — Dokploy supports IANA timezone names (e.g., Europe/Prague). If you set that, the cron will run in that timezone instead of UTC [3].

To reply, just mention @dosu.

Share context across your team and agents. Try Dosu.

Hey, you can set a timezone, read here https://docs.dokploy.com/docs/core/manual-installation#setup-dokploy-timezone

Thank you all for exhaustive explanation.

But this is my point, cron is set to : 15 4 * * *, but UI timestamp says the schedules were running at 6:15.
So my guess was that 6:15 was my local time, not the UTC.