AlexanderVarlamov opened a new issue, #57488:
URL: https://github.com/apache/airflow/issues/57488
### Apache Airflow version
Other Airflow 2/3 version (please specify below)
### If "Other Airflow 2/3 version" selected, which one?
2.10.5
### What happened?
I have this DAG:
dag = DAG(dag_id='orch_stop',
description='set_orch_limits_to_zero',
catchup=False,
schedule=CronTriggerTimetable('45 20 * * 5',
timezone='Europe/Moscow'),
start_date=datetime(2025, 1, 31, 20, 35),
render_template_as_native_obj=True,
max_active_runs=1,
max_active_tasks=1,
is_paused_upon_creation=True,
doc_md=doc_md,
)
It should start on Friday on 20.45. On Friday 21.02.2025 approximately on
17.00 I turned it off. But when I switch it on Monday, it ran immediately.
Why?
I haven't schedule interval cause I use CronTriggerTimetable. I set catchup
to False. I read many articles, but all I have found was there was a bug in old
AF versions. Isn't it fixed yet?
What's wrong with my Dag? What should I do to prevent that behavior in
future?
And globally every dag immediately starts when I turned it on. Is it right
behavior?
### What you think should happen instead?
I suppose the dag should start on his cron only.
### How to reproduce
You can create dag with settings above and check.
### Operating System
Linux Redos/Centos
### Versions of Apache Airflow Providers
_No response_
### Deployment
Docker-Compose
### Deployment details
_No response_
### Anything else?
_No response_
### 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]
