Skip to content

Fix Slack alerts not firing for declarative pipeline tasks#68

Merged
mrhallak merged 1 commit intomasterfrom
fix/declarative-pipeline-slack-alerts
Feb 12, 2026
Merged

Fix Slack alerts not firing for declarative pipeline tasks#68
mrhallak merged 1 commit intomasterfrom
fix/declarative-pipeline-slack-alerts

Conversation

@mrhallak
Copy link

Summary

  • The DatabricksRunNowOperator in DeclarativePipelineCreator was setting on_failure_callback=_cancel_databricks_run directly on the operator, which overrides the DAG-level on_failure_callback (Slack alerts) from default_args
  • Added _build_failure_callback() that creates a composite callback: cancels the Databricks run and invokes the DAG-level alert callback (e.g. Slack notifications)
  • When no DAG-level callback is configured, behavior is unchanged (only _cancel_databricks_run)

Test plan

  • All 18 declarative pipeline creator tests pass (4 new + 14 existing)
  • Full dagger test suite passes (pre-existing failures unrelated)
  • Deploy to datastg and trigger a failure to verify Slack alert fires

The on_failure_callback on DatabricksRunNowOperator was overriding
the DAG-level callback (Slack alerts) set in default_args. Build a
composite callback that cancels the Databricks run AND invokes the
DAG-level alert callback.
@mrhallak mrhallak requested a review from a team as a code owner February 12, 2026 10:12
@mrhallak mrhallak merged commit 4a89d44 into master Feb 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants