potiuk commented on issue #31687: URL: https://github.com/apache/airflow/issues/31687#issuecomment-1621520766
> In this issue, airflow doesn't create runs for the whole days/runs - it acts like the dag is disabled and skips days/runs. I **think** that might still be related. Simply some subtle bug (like running the schedule precisely at the very moment it should be scheduled) might trigger it. For some reason you seem to have an installation where this behaviour seems to be easily reproducible, so maybe we can use it to narrow down the issue. I think @hussein-awala was right it would be great if you could try to reproduce it with old expression and catchup = False. From what I understand above, `catchup =True` actully solves the problem. If we could know that also the old schedule does (independently from catchup = True), it could help to narrrow down the issue. Also cc: @uranusjr -> It really looks like some edge-case i CronTriggerTimetable from the description and helpful experiments done by @ibardarov-fms . The 14 seconds delay in queue time shows that likely there might be a race condition that gets triggered somewhere by the timetable. -- 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]
