potiuk commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-2167567219
> Unfortunately, I don't think I have the resources currently to get
familiar with the source code and implement this.
No worries - it's marged as good first issue, so
cedric-fauth commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-2167437319
Unfortunately, I don't think I have the resources currently to get familiar
with the source code and implement this.
--
This is an automated message from the Apache Git
potiuk commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-2163140507
> Hi, we have the same issue with airflow. I understand this is expected but
it would be a great enhancement if there was a feature to turn off the
immediate-run behavior when
cedric-fauth commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-2160665825
> In our pipeline, we occasionally disable some DAGs to prevent them from
executing. Another use case is during testing, based on the value of a
variable, I decide which DAG
jens-scheffler-bosch commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-1785311234
> Is that expected that DAGs trigger immediately for last scheduled task
even catchup=False once they are re-enabled since 2.7 for
DeltaDataIntervalTimetable?
William-Yi-Weng commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-1784365993
Is that expected that DAGs trigger immediately for last scheduled task even
catchup=True once they are re-enabled since 2.7 for DeltaDataIntervalTimetable?
--
This is an
Taragolis commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-1783503719
You might play with different [builtin
Timetables](https://airflow.apache.org/docs/apache-airflow/stable/authoring-and-scheduling/timetable.html#timetables),
e.g.
Taragolis commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-1783498514
That is always depends on requirements, if DAG intend to use as scheduled
then you need to enable it (unpause), if you need manually run newly created
DAG which intends to be
q121212 commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-1783455157
but this is strange, because there is no way to enable a dag that runs on a
schedule so that it does not start additionally
--
This is an automated message from the Apache Git
Taragolis commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-1783344715
Yep in this case 1 would be for scheduling execution (it could be more if
catchup=True) and another for manual
--
This is an automated message from the Apache Git Service.
To
q121212 commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-1783250123
> > After push play button DAG should be triggered only one time
>
> It is intended behaviour if in `schedule` defined cron expression or
timetable.
yes, my dags have
Taragolis commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-1783240045
> After push play button DAG should be triggered only one time
It is intended behaviour if in `schedule` defined cron expression or
timetable.
--
This is an automated
boring-cyborg[bot] commented on issue #35220:
URL: https://github.com/apache/airflow/issues/35220#issuecomment-1783186145
Thanks for opening your first issue here! Be sure to follow the issue
template! If you are willing to raise PR to address this issue please do so, no
need to wait for
q121212 opened a new issue, #35220:
URL: https://github.com/apache/airflow/issues/35220
### Apache Airflow version
2.7.2
### What happened
Problems that I discovered: 1) If DAG is on pause, then when you go into it
and unpause it with the button on the left, the DAG
14 matches
Mail list logo
