OptionalattemptThe sequence number of this run attempt for a triggered job run. The initial attempt of a run has an attempt_number of 0. If the initial run attempt fails, and the job has a retry policy (max_retries > 0), subsequent runs are created with an original_attempt_run_id of the original attempt’s ID and an incrementing attempt_number. Runs are retried only until they succeed, and the maximum attempt_number is the same as the max_retries value for the job.
OptionalcleanupThe time in milliseconds it took to terminate the cluster and clean up any associated artifacts. The duration of a task run is the sum of the setup_duration, execution_duration, and the cleanup_duration. The cleanup_duration field is set to 0 for multitask job runs. The total duration of a multitask job run is the value of the run_duration field.
OptionalclusterThe cluster used for this run. If the run is specified to use a new cluster, this field is set once the Jobs service has requested a cluster for the run.
OptionalcomputeTask level compute configuration.
OptionaldependsAn optional array of objects specifying the dependency graph of the task. All tasks specified in this field must complete successfully before executing this task.
The key is task_key, and the value is the name assigned to the dependent task.
OptionaldescriptionAn optional description for this task.
OptionaldisableAn option to disable auto optimization in serverless
OptionaldisabledAn optional flag to disable the task. If set to true, the task will not run even if it is part of a job.
OptionaleffectiveThe actual performance target used by the serverless run during execution. This can differ from the client-set performance target on the request depending on whether the performance mode is supported by the job type.
STANDARD: Enables cost-efficient execution of serverless workloads.PERFORMANCE_OPTIMIZED: Prioritizes fast startup and execution times through rapid scaling and optimized cluster performance.OptionalemailAn optional set of email addresses notified when the task run begins or completes. The default behavior is to not send any emails.
OptionalendThe time at which this run ended in epoch milliseconds (milliseconds since 1/1/1970 UTC). This field is set to 0 if the job is still running.
OptionalenvironmentThe key that references an environment spec in a job. This field is required for Python script, Python wheel and dbt tasks when using serverless compute.
OptionalexecutionThe time in milliseconds it took to execute the commands in the JAR or notebook until they completed, failed, timed out, were cancelled, or encountered an unexpected error. The duration of a task run is the sum of the setup_duration, execution_duration, and the cleanup_duration. The execution_duration field is set to 0 for multitask job runs. The total duration of a multitask job run is the value of the run_duration field.
OptionalgitAn optional specification for a remote Git repository containing the source code used by tasks. Version-controlled source code is supported by notebook, dbt, Python script, and SQL File tasks. If git_source is set, these tasks retrieve the file from the remote repository by default. However, this behavior can be overridden by setting source to WORKSPACE on the task. Note: dbt and SQL File tasks support only version-controlled sources. If dbt or SQL File tasks are used, git_source must be defined on the job.
OptionalhealthOptionallibrariesAn optional list of libraries to be installed on the cluster. The default value is an empty list.
OptionalmaxAn optional maximum number of times to retry an unsuccessful run. A run is considered to be unsuccessful if it completes with the FAILED result_state or INTERNAL_ERROR life_cycle_state. The value -1 means to retry indefinitely and the value 0 means to never retry.
OptionalminAn optional minimal interval in milliseconds between the start of the failed run and the subsequent retry run. The default behavior is that unsuccessful runs are immediately retried.
OptionalnotificationOptional notification settings that are used when sending notifications to each of the email_notifications and webhook_notifications for this task run.
OptionalqueueThe time in milliseconds that the run has spent in the queue.
OptionalresolvedParameter values including resolved references
OptionalretryAn optional policy to specify whether to retry a job when it times out. The default behavior is to not retry on timeout.
OptionalrunThe time in milliseconds it took the job run and all of its repairs to finish.
OptionalrunThe ID of the task run.
OptionalrunAn optional value indicating the condition that determines whether the task should be run once its dependencies have been completed. When omitted, defaults to ALL_SUCCESS. See :method:jobs/create for a list of possible values.
OptionalrunOptionalsetupThe time in milliseconds it took to set up the cluster. For runs that run on new clusters this is the cluster creation time, for runs that run on existing clusters this time should be very short. The duration of a task run is the sum of the setup_duration, execution_duration, and the cleanup_duration. The setup_duration field is set to 0 for multitask job runs. The total duration of a multitask job run is the value of the run_duration field.
OptionalspecIf existing_cluster_id, the ID of an existing cluster that is used for all runs. When running jobs or tasks on an existing cluster, you may need to manually restart the cluster if it stops responding. We suggest running jobs and tasks on new clusters for greater reliability
If new_cluster, a description of a new cluster that is created for each run.
If job_cluster_key, this task is executed reusing the cluster specified in job.settings.job_clusters.
OptionalstartThe time at which this run was started in epoch milliseconds (milliseconds since 1/1/1970 UTC). This may not be the time when the job task starts executing, for example, if the job is scheduled to run on a new cluster, this is the time the cluster creation call is issued.
OptionalstateDeprecated. Please use the status field instead.
OptionalstatusOptionaltaskDO NOT ADD ANY NEW FIELDS TO JobTask OUTSIDE OF THIS ONEOF as it will break the TaskRegistry
The task runs a notebook when the notebook_task field is present.
The task runs a JAR when the spark_jar_task field is present.
The task runs a Python file when the spark_python_task field is present.
(Legacy) The task runs the spark-submit script when the spark_submit_task field is present. Databricks recommends using the spark_jar_task instead; see Spark Submit task for jobs.
The task triggers a pipeline update when the pipeline_task field is present. Only pipelines configured to use triggered more are supported.
The task runs a Python wheel when the python_wheel_task field is present.
The task runs one or more dbt commands when the dbt_task field is present. The dbt task requires both Databricks SQL and the ability to use a serverless or a pro SQL warehouse.
The task runs a SQL query or file, or it refreshes a SQL alert or a legacy SQL dashboard when the sql_task field is present.
The task triggers another job when the run_job_task field is present.
The task evaluates a condition that can be used to control the execution of other tasks when the condition_task field is present.
The condition task does not require a cluster to execute and does not support retries or notifications.
The task executes a nested task for every input provided when the for_each_task field is present.
The task runs a clean rooms notebook
when the clean_rooms_notebook_task field is present.
The task evaluates a alert_task field is present.
The task triggers a Power BI semantic model update when the power_bi_task field is present.
The task refreshes a dashboard and sends a snapshot to subscribers.
Task type for dbt cloud, deprecated in favor of the new name dbt_platform_task
The task runs a Python operator task.
OptionaltaskA unique name for the task. This field is used to refer to this task from other tasks. This field is required and must be unique within its parent job. On Update or Reset, this field is used to reference the tasks to be updated or reset.
OptionaltimeoutAn optional timeout applied to each run of this job task. A value of 0 means no timeout.
OptionalwebhookA collection of system notification IDs to notify when the run begins or completes. The default behavior is to not send any system notifications. Task webhooks respect the task notification settings.
Used when outputting a child run, in GetRun or ListRuns.