diederikvdv opened a new issue, #43547:
URL: https://github.com/apache/airflow/issues/43547
### Apache Airflow version
2.10.2
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
When manually retriggering a DAG, the passed logical_date seems partly
interpreted as data_interval_start and partly as data_interval_end
Context: I have a DAG run that fails and want to retrigger it on the exact
same moment as the schedule, but with different parameters. During this process
I encountered the what I believe is buggy behaviour.
Strange behaviour 1:
1. A scheduled monthly DAG run has finished with:
- Data interval start | 2024-09-01, 00:00:00 CEST
- Data interval end | 2024-10-01, 00:00:00 CEST
2. I trigger the DAG again where I fill the logical_date with the
data_interval_start
3. It throws the following error: "The logical date [...] already exists"
Strange behaviour 2:
1. A scheduled monthly DAG run has finished with:
- Data interval start | 2024-09-01, 00:00:00 CEST
- Data interval end | 2024-10-01, 00:00:00 CEST
2. I trigger the DAG again where I fill the logical_date with the
data_interval_end
3. It triggers a run with the same data_interval_end and data_interval_start
as the scheduled run
4. The sensor we have in place however pokes an unexpected date:
- The scheduled poke date was: 2024-08-31T22:00:00+00:00
- The triggered poke date was: 2024-09-30T22:00:00+00:00
### What you think should happen instead?
Behaviour 1:
<img width="1701" alt="image"
src="https://github.com/user-attachments/assets/17c5a80c-e732-4bf0-b667-392db8590322";>
I expected this error to be thrown in the case of filling the
data_interval_end, not in the case of the data_interval_start. Because if I
fill the data_interval_end, I get the data_interval_start and data_interval_end
of the already scheduled DAG run as well as the same run name of that DAG run
Behaviour 2:
<img width="1691" alt="image"
src="https://github.com/user-attachments/assets/7c1550f2-6b91-4c82-a74d-8c54acd193bb";>
I expected the error of behaviour 1 to be thrown here.
I expected the sensor to poke depending on the data_interval_start not based
on the data_interval_end
<img width="725" alt="image"
src="https://github.com/user-attachments/assets/93ec1f08-085f-4dba-a20e-97a12a9c0d62";>
<img width="713" alt="image"
src="https://github.com/user-attachments/assets/79dc2325-8859-4927-8404-6dccc9b3e325";>
### How to reproduce
See "What happened"
### Operating System
Debian GNU/Linux 11 (bullseye)
### Versions of Apache Airflow Providers
_No response_
### Deployment
Docker-Compose
### Deployment details
_No response_
### Anything else?
( Probably has overlap with https://github.com/apache/airflow/issues/41014 ?)
### Are you willing to submit PR?
- [ ] 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]
