[
https://issues.apache.org/jira/browse/AIRFLOW-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jack updated AIRFLOW-3563:
--------------------------
Affects Version/s: (was: 1.10.1)
1.10.2
Component/s: ui
> schedule_interval to raise error like broken DAG
> ------------------------------------------------
>
> Key: AIRFLOW-3563
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3563
> Project: Apache Airflow
> Issue Type: Task
> Components: ui
> Affects Versions: 1.10.2
> Reporter: jack
> Priority: Major
>
> I added a DAG with the following parameters:
>
> {code:java}
> schedule_interval='0 30 * * *'{code}
>
>
> I started the DAG manually.
> In {color:#333333}DAG Runs {color}{color:#333333}column it's running but
> in{color}{color:#333333} Recent Tasks {color}{color:#333333}no tasks are
> being scheduled.{color}
> {color:#333333}This happens because there is an error (found on logs){color}
> {code:java}
> Traceback (most recent call last):
> File "/usr/local/lib/python2.7/dist-packages/croniter/croniter.py", line
> 538, in expand
> expr_format))
> CroniterBadCronError: [0 30 * * *] is not acceptable, out of range{code}
>
> This error is in the DAG definition (wrong interval input) it should be shown
> as a *Broken DAG* alert in red at the UI. The problem here is that this DAG
> seems to be running but actually it's not. It's very weird that the DAG
> appear like it's running while it logs errors that prevents it from being run.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
