gmuenchCB commented on PR #33404:
URL: https://github.com/apache/airflow/pull/33404#issuecomment-1875730551
> > The docs are wrong. I have been hoping to make a PR to fix them but
hadn't had a chance.
>
> In this case, I would say the behavior described in the docs should be the
actu
shubham22 commented on PR #33404:
URL: https://github.com/apache/airflow/pull/33404#issuecomment-1874456165
> The docs are wrong. I have been hoping to make a PR to fix them but hadn't
had a chance.
In this case, I would say the behavior described in the docs should be the
actual beh
fatmumuhomer commented on PR #33404:
URL: https://github.com/apache/airflow/pull/33404#issuecomment-1872645280
@potiuk, @o-nikolas The original behavior of the CronTriggerTimetable was as
described in the docs and as described as the expected behavior in
https://github.com/apache/airflow/di
potiuk commented on PR #33404:
URL: https://github.com/apache/airflow/pull/33404#issuecomment-1872502694
But the decription quoted by the user contradicts it IMHO
https://airflow.apache.org/docs/apache-airflow/stable/authoring-and-scheduling/timetable.html#the-time-when-a-dag-run-is-triggere
potiuk commented on PR #33404:
URL: https://github.com/apache/airflow/pull/33404#issuecomment-1872501665
I am not sure, but I think it was the opposite problem. And I am not
entirely sure what's the CronTimetable expected behaviour it - it's not
explained in
https://airflow.apache.org/docs
o-nikolas commented on PR #33404:
URL: https://github.com/apache/airflow/pull/33404#issuecomment-1864975964
Regarding this Q&A discussion:
https://github.com/apache/airflow/discussions/35647
Could this change be the cause? I've also received feedback from MWAA
customer that the CronT
