avkirilishin commented on pull request #21684: URL: https://github.com/apache/airflow/pull/21684#issuecomment-1048797182
> I don't think this is the right fix. If I understand correctly, the problem is that the scheduler is creating dagruns for those past dates and not that the task instances are being scheduled. The ExecDateAfterStartDateDep currently in place will prevent tasks from getting into queued state if the start date is before the execution date I explained it here: https://github.com/apache/airflow/issues/20461#issuecomment-1046051990 > I think there are two different problems: > > The problem is related to the different logic of the scheduler before and after the update. Maybe there are no tasks in the running dags or something else. Can you show the rows for this dag run in dag, dag_run and task_instance? > > _**I agree with you that it is not the right behavior for the scheduler to continue scheduling runs that are earlier than the actual start date of the DAG or Task. It can happen, for example, after turning the dag off and back on. So I made a PR to fix it: https://github.com/apache/airflow/pull/21684**_ -- 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]
