Skip to content

fix(backend): load workflow notification_config instead of empty default#3171

Merged
mrveiss merged 1 commit intoDev_new_guifrom
issue-3168
Apr 1, 2026
Merged

fix(backend): load workflow notification_config instead of empty default#3171
mrveiss merged 1 commit intoDev_new_guifrom
issue-3168

Conversation

@mrveiss
Copy link
Copy Markdown
Owner

@mrveiss mrveiss commented Apr 1, 2026

Closes #3168

Summary

  • Added _resolve_notification_config() that reads config from execution_context
  • Supports both NotificationConfig objects and raw dicts
  • Returns None (skip notifications) when no config is present
  • _send_step_failure_notification now receives execution_context for config lookup

Root Cause

PR #3130 created empty NotificationConfig(workflow_id=...) with no channels/recipients, so notifications were silently dropped by the service.

Test plan

  • Python syntax validated
  • CI passes
  • Workflow with notification_config sends notifications on completion/failure

🤖 Generated with Claude Code

#3168)

Replace empty NotificationConfig with _resolve_notification_config()
that reads notification_config from execution_context. Notifications
now only fire when the workflow has a configured notification_config,
preventing silent no-ops.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@mrveiss mrveiss merged commit 04be4ee into Dev_new_gui Apr 1, 2026
2 of 4 checks passed
@mrveiss mrveiss deleted the issue-3168 branch April 1, 2026 18:18
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.

1 participant