Open hvignolo87 opened 1 year ago
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
The issue lies here: we aren't applying restrictions from a DAG when evaluating SLAs. This problem can occur not only in the ContinuousTimeTable but also in other timetables, such as OnceTimetable.
While it could be fixed, I believe it would be better to wait for the SLA refactoring in #32816.
Apache Airflow version
Airflow version: 2.6.3-python3.10
What happened
It seems that SLA is not checked when setting
schedule="@continuous"
in Airflow 2.6.3.What you think should happen instead
SLA miss must be shown in the SLA Misses section, and the
sla_miss_callback
function triggered.How to reproduce
Run this DAG:
After some DagRuns, go to Browse/SLA Misses and verify that there's no SLA Miss registered. Also, yo can perform a similar check by creating a simple
sla_miss_callback
function, and verifying it's not been triggered.Operating System
macOS Sonoma 14.0
Versions of Apache Airflow Providers
Deployment
Docker-Compose
Deployment details
docker-compose.yaml
(SLA check is enabled)Dockerfile.local
Anything else
I've tested the callback function also, and it doesn't work either. If you change to a CRON schedule, both things works fine.
Are you willing to submit PR?
Code of Conduct