[
https://issues.apache.org/jira/browse/AIRFLOW-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279559#comment-15279559
]
nirav pranami commented on AIRFLOW-67:
--------------------------------------
I ran *airflow scheduler -n 5*
Below is the info I got for *my_dag*
{quote}
[2016-05-11 05:02:05,014] {models.py:2274} INFO - Checking state for <DagRun
*conversion_event_report* @ 2016-04-23 00:00:00:
scheduled__2016-04-23T00:00:00, externally triggered: False>
[2016-05-11 05:02:05,017] {models.py:2274} INFO - Checking state for <DagRun
*conversion_event_report* @ 2016-04-21 00:00:00:
scheduled__2016-04-21T00:00:00, externally triggered: False>
[2016-05-11 05:02:05,019] {models.py:2274} INFO - Checking state for <DagRun
*conversion_event_report* @ 2016-04-22 00:00:00:
scheduled__2016-04-22T00:00:00, externally triggered: False>
{quote}
> Dag is not avaialble on UI
> --------------------------
>
> Key: AIRFLOW-67
> URL: https://issues.apache.org/jira/browse/AIRFLOW-67
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: nirav pranami
>
> Dear Airflow Maintainers,
> Before I tell you about my issue, let me describe my Airflow environment:
> Airflow version: 1.7.0
> Airflow components: CeleryExecutor
> Python Version: 2.7.6
> Operating System: Centos
> Description of Issue
> Now that you know a little about me, let me tell you about the issue I am
> having:
> I am not able to see a new dag I wrote on the web-UI. The dag shows up in the
> *airflow list_dags* output.
> I am able to see all other dags that I wrote previously. Though, the dag
> starts executing because some of the tasks move into *running* state.
> The new dag is not click-able and has the below info.
> {quote}
> This DAG isn't available in the web server's DagBag object. It shows up in
> this list because the scheduler marked it as active in the metadata database.
> {quote}
> I had similar experience with a dag I published before this one. But, that
> one became available after about a day.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
