matthieuauger opened a new issue, #49790:
URL: https://github.com/apache/airflow/issues/49790
### Apache Airflow version
3.0.0
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
Hello, this is probably a configuration issue somewhere because I don't
think this could not work but this was functional with Airflow 2.8, not with
Airflow 3.0 and every documentation I find tell me that current behaviour is
not as expected. If this is something obvious, thanks and my apologies.
I have a really simple DAG with following configuration, schedule='@daily'
`@dag(
'example_dag',
schedule='@daily',
start_date=datetime(2025, 4, 23),
catchup=True,
)
def example_dag():
@task(task_id='no_op')
def no_op() -> List[Dict]:
logger = LoggingMixin().log
logger.info("no op")
dag = example_dag()
`
When I activate the DAG, there are 3 scheduled runs, as expected.
But data_interval_start is not set to Day-1 but to the same value that
data_interval_end. This is true for every run.
I tried to play with several configuration, changing to cron format,
removing catchup, etc but I always have same start and end execution date. Is
there something wrong with this configuration?
Here is detailled configuration for a run if that can help.
### What you think should happen instead?
If I put a DAG as daily and a run is scheduled, data_interval_start should
be N-1, or at least data_interval_start and data_interval_end should not be
equal
### How to reproduce
Use the same DAG
### Operating System
Docker
### Versions of Apache Airflow Providers
_No response_
### Deployment
Docker-Compose
### 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]
