cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Job start time timezone

Guigui
New Contributor II

It is mentionned in the documentation that the job.start_time is a value of time in UTC timezone but I wonder if it's always the case because as the start_time is in UTC timezone for a scheduled job, it is in local timezone when it is manually triggered. How to know in which context we are (triggered vs manual) or how to know the timezone of this time ?

3 REPLIES 3

Mounika_Tarigop
Databricks Employee
Databricks Employee

The job.start_time value in Databricks is indeed in UTC timezone as mentioned in the documentation. However, there is a distinction based on how the job is triggered. The trigger attribute will indicate whether the job was triggered manually or by a schedule.

  • If the trigger attribute is set to SCHEDULED, the job.start_time is in UTC.
  • If the trigger attribute is set to MANUAL, the job.start_time is in the local timezone of the user who triggered the job

 

Thanks Mounika, 
That's actually my understanding. And how to know whether the job was triggered manually or by schedule ? Is there a parameter with a dynamic value for that?

Mounika_Tarigop
Databricks Employee
Databricks Employee

To determine whether a Databricks job was triggered manually or by schedule, you can use the dynamic value reference {{job.trigger.type}}. T

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now