Found a potential bug in Job Details/Schedule and Trigger section

Katalin555 — Wed, 02 Apr 2025 09:51:58 GMT

One of our jobs is scheduled to run at 4:30 AM based on GMT+1 timezone, which is visible if we click on the Edit trigger (Picture1), but under job details it is show as if it was schedule to run at 4:30 AM UTC time (Picture 2).

Based on previous runs it actually run at 4:30 AM (UTC).

Picture 1

Picture 2

Picture 3

Re: Found a potential bug in Job Details/Schedule and Trigger section

Isi — Thu, 03 Apr 2025 22:53:54 GMT

Hey @Katalin555

Even though in the “Edit Trigger” panel (Picture 2) the time is shown in local timezone (e.g. GMT+1), once the schedule is saved and viewed under job details (Picture 1), Databricks always displays it as UTC — without making it visually obvious that it was converted.

So in your case:

You configured the job to run at 4:30 AM GMT+1.
That translates to 3:30 AM UTC, and Databricks shows this as “Paused - At 4:30 AM (UTC+00:00)”, which is misleading.
However, if you check the actual execution time, you’ll notice that it really runs at 3:30 AM UTC, which matches the expected GMT+1 time you wanted.

This is just a UI inconsistency — the scheduler uses the timezone correctly, but the labels in the job summary panel always show UTC without clarifying the conversion...

They should fix it... 😞

Isi

topic Found a potential bug in Job Details/Schedule and Trigger section in Data Engineering

Found a potential bug in Job Details/Schedule and Trigger section

Re: Found a potential bug in Job Details/Schedule and Trigger section