Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Triggering DAG from UI Creates 2 DAG runs if the DAG was paused
See original GitHub issueApache Airflow version
2.3.2 (latest released)
What happened
If a DAG with a schedule_interval set to @daily is paused, and the DAG is triggered by clicking the “play” button --> “Trigger DAG”, two DAG runs will simultaneously be triggered: One for the current data interval and one for the manual run.
What you think should happen instead
Maybe an alert with confirmation should pop up and inform the user that the DAG run will be for the current data interval rather than the current datetime?
How to reproduce
- Pause a DAG that hasn’t run in the current data interval.
- Trigger the DAG by clicking the “play” button then clicking “Trigger DAG”
Operating System
Debian 11
Versions of Apache Airflow Providers
n/a
Deployment
Astronomer
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
- I agree to follow this project’s Code of Conduct
Issue Analytics
- State:
- Created a year ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi @potiuk please assign it to me.
@rohit-mobstac If DAG is turned on within the DAG’s data interval, it will trigger a DAG run when you unpause the DAG, which I think is to be expected. I think there should be some kind of logic that blocks that scheduled DAG run to run if you’re triggering it from the UI. Or there should at least be the option to block it.