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