You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Bolke de Bruin (JIRA)" <ji...@apache.org> on 2018/01/19 17:54:00 UTC

[jira] [Resolved] (AIRFLOW-511) DagRun Failure: Retry, Email, Callbacks

     [ https://issues.apache.org/jira/browse/AIRFLOW-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bolke de Bruin resolved AIRFLOW-511.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.0

Issue resolved by pull request #2934
[https://github.com/apache/incubator-airflow/pull/2934]

> DagRun Failure: Retry, Email, Callbacks
> ---------------------------------------
>
>                 Key: AIRFLOW-511
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-511
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Rob Froetscher
>            Assignee: Ace Haidrey
>            Priority: Minor
>             Fix For: 1.10.0
>
>
> Are there any plans to have retry, email, or callbacks on failure of a DAG run? Would you guys be open to someone implementing that? Right now particularly with dagrun_timeout, there is not much insight that the dag actually stopped.
> Pseudocode: https://github.com/apache/incubator-airflow/compare/master...rfroetscher:dagrun_failure



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)