Email Notifications
Usage
email_notifications(
on_start = NULL,
on_success = NULL,
on_failure = NULL,
no_alert_for_skipped_runs = TRUE
)Arguments
- on_start
List of email addresses to be notified when a run begins. If not specified on job creation, reset, or update, the list is empty, and notifications are not sent.
- on_success
List of email addresses to be notified when a run successfully completes. A run is considered to have completed successfully if it ends with a
TERMINATEDlife_cycle_stateand aSUCCESSFULresult_state.If not specified on job creation, reset, or update, the list is empty, and notifications are not sent.- on_failure
List of email addresses to be notified when a run unsuccessfully completes. A run is considered to have completed unsuccessfully if it ends with an
INTERNAL_ERRORlife_cycle_stateor aSKIPPED,FAILED, orTIMED_OUTresult_state.If this is not specified on job creation, reset, or update the list is empty, and notifications are not sent.- no_alert_for_skipped_runs
If
TRUE(default), do not send email to recipients specified inon_failureif the run is skipped.
See also
Other Task Objects:
condition_task(),
for_each_task(),
libraries(),
new_cluster(),
notebook_task(),
pipeline_task(),
python_wheel_task(),
run_job_task(),
spark_jar_task(),
spark_python_task(),
spark_submit_task(),
sql_file_task(),
sql_query_task()
