sla_miss_callback not triggered when SLA is missed #47040
Unanswered
sam-gen-cop
asked this question in
General
Replies: 1 comment 3 replies
-
Hard to help you - looks good, but not sure where you look for logs. Possibly the log appars in scheduler/dag processor logs. Left it for discussion but I think that's your probem. Also SLA MISS is generated AFTER task completes - which is a known problems with SLAs. Airflow 3 is dropping SLAs conmpletely and there will be a new "deadline" feature. https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=323488182 |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Apache Airflow version
Other Airflow 2 version (please specify below)
If "Other Airflow 2 version" selected, which one?
2.10.1
What happened?
I have added a custom SLA callback function to the DAG script, which is supposed to trigger when the task breaches the SLA defined. However, the callback function is not getting triggered. Please tell me where I'm going wrong.
What you think should happen instead?
No response
How to reproduce
Script used to test the callback,
Operating System
NA
Versions of Apache Airflow Providers
apache-airflow-providers-amazon - 8.28.0
apache-airflow-providers-celery - 3.8.1
apache-airflow-providers-common-compat - 1.2.0
apache-airflow-providers-common-io - 1.4.0
apache-airflow-providers-common-sql - 1.16.0
apache-airflow-providers-fab - 1.3.0
apache-airflow-providers-ftp - 3.11.0
apache-airflow-providers-http - 4.13.0
apache-airflow-providers-imap - 3.7.0
apache-airflow-providers-postgres - 5.12.0
apache-airflow-providers-smtp - 1.8.0
apache-airflow-providers-sqlite - 3.9.0
Deployment
Amazon (AWS) MWAA
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions