blinkseb commented on issue #18880:
URL: https://github.com/apache/airflow/issues/18880#issuecomment-1042686485
Hello everyone, sorry for not answering later, the upgrade to 2.2.0 was a
bit harder than expected with the timetable changes!
Unfortunately, we still experience the same issue. The DAG would trigger as
expected, but none of the task would run. I've been able to capture a debug log
when the DAG is triggered:
```
[2022-02-13 23:02:50,016] {dag.py:2935} INFO - Setting next_dagrun for
optimhome_fr_404 to 2022-02-12T23:21:00+00:00
[2022-02-13 23:02:50,040] {scheduler_job.py:1058} DEBUG - DAG
optimhome_fr_404 not changed structure, skipping dagrun.verify_integrity
[2022-02-13 23:02:50,048] {dagrun.py:622} DEBUG - number of tis tasks for
<DagRun optimhome_fr_404 @ 2022-02-11 23:21:00+00:00:
scheduled__2022-02-11T23:21:00+00:00, externally triggered: False>: 0 task(s)
[2022-02-13 23:02:50,048] {dagrun.py:545} INFO - Marking run <DagRun
optimhome_fr_404 @ 2022-02-11 23:21:00+00:00:
scheduled__2022-02-11T23:21:00+00:00, externally triggered: False> successful
[2022-02-13 23:02:50,048] {dagrun.py:590} INFO - DagRun Finished:
dag_id=optimhome_fr_404, execution_date=2022-02-11 23:21:00+00:00,
run_id=scheduled__2022-02-11T23:21:00+00:00, run_start_date=2022-02-13
23:02:50.029131+00:00, run_end_date=2022-02-13 23:02:50.048701+00:00,
run_duration=0.01957, state=success, external_trigger=False,
run_type=scheduled, data_interval_start=2022-02-11 23:21:00+00:00,
data_interval_end=2022-02-12 23:21:00+00:00,
dag_hash=d2e4af2c86c72402eebb911e5269818b
```
one intriguing line is `number of tis tasks for <DAG>: 0 task(s)`, except
there are tasks on the DAG as you can see on this screenshot

I've not been able to figure out (yet) where the tasks instances are created
in the code. Maybe you can point me to the right direction so I can investigate
further?
Thanks a lot!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]