@ancient-wolf-19325 I am trying to get slack notifications work with launchplan. Slack accepts emails but flyte is not sending them successfully

notifications=[
        Slack(
            phases=[
                WorkflowExecutionPhase.FAILED,
                WorkflowExecutionPhase.TIMED_OUT,
            ],
            recipients_email=[SLACK_EMAIL],
        ),
    ],

Flyte supports Slack notifications by sending emails to a Slack channel's email address, configured via the

Slack

notification object in a launch plan. However, for this to work, your Flyte deployment must be properly configured to send notification emails (e.g., via AWS SES, SendGrid, or SMTP), and the Slack channel must have an email integration enabled. If emails are not being sent, it's likely due to missing or incorrect notification backend configuration, or issues with the email service setup—not with the Flyte launch plan code itself. See notification configuration docs and Slack integration instructions. If you need a code example or troubleshooting steps, let me know. Sources: - Configuring notifications 👍 1 button 👎 0 button 💡 Hint: Mention @ancient-wolf-19325 in the thread for followups.

@powerful-australia-73346 have you tried with webhook?

@average-finland-92144 I get it working locally but not in flyte in kube. Does it require something else than updating python package `flytekit versions (

>=1.15.0

)`

depending on the notifications provider you're using you might need to add configuration under the

workflow_notifications

section in the Helm values What Helm chart you used to install Flyte?

@average-finland-92144 Got it working but very differently than in docs. Cant use it from

workflow

level. If a

task

fails to a test exception like in docs,

try, except

never catches it. But if I

try except

in the

task

it works.

could you share a reproducible code snippet? Static workflows in Flyte do not support `try`/`except` logic (this might change dramatically in the near future)

@average-finland-92144 Interesting so the example

workflow

in https://github.com/flyteorg/flytekit/pull/3058 is not static then?

ah my bad, I got my wires crossed

Nope, do not even have

flyteconnector

block

is it flyte-core or flyte-binary?

ok, so if there is no flyteconnector block in your values, you are not overriding the base values, which defaults to disable add that to your values and upgrade the Helm installed release

flyteconnector:
  enabled: true

I will try that. What does the

flyteconnector

do. I did not find documentation describing what it does enabled vs disabled