wanlce opened a new issue #21594: URL: https://github.com/apache/airflow/issues/21594
### Apache Airflow version main (development) ### What happened New version of the timetables issue eg: At first I had a scheduling time of 30 * * * * * After running it twice, I changed it to 32 * * * * The actual first run time after the change is fine, but because the data interval starts from the end of the previous interval, it has already been determined and not refreshed, so the displayed execution_date is incorrect. This can cause problems with Cross-dag dependencies.  |  --- | --- Correct:  |  --- | --- https://github.com/apache/airflow/blob/f1db4524deb0ec354d3561e8ad22f81c7d08bc3c/airflow/timetables/interval.py#L93-L97 My current solution is to add start = self._get_prev(end) below end = self._get_next(start) to reset data_interval_start. I'm not sure if this is appropriate Looking forward to new ideas ### What you expected to happen _No response_ ### How to reproduce _No response_ ### Operating System ubuntu21.10 ### Versions of Apache Airflow Providers _No response_ ### Deployment Virtualenv installation ### Deployment details _No response_ ### Anything else _No response_ ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
