<@U06RKAMK0UC> i have flyte deployed in AKS. The N...
# ask-ai
p
@ancient-wolf-19325 i have flyte deployed in AKS. The Notification feature (configured in flyte admin) is not supported in Azure deployments so I'm looking at
WebhookTask
to fire messages if there are failures. is there a pattern or configuration that allows me to call the webhook based on the workflow end-state, as opposed to catching an exception in a task?
a
There is no built-in Flyte configuration or pattern that allows a
WebhookTask
to be automatically triggered based on the workflow end-state (e.g., success or failure) at the workflow level.
WebhookTask
is designed to be invoked as a regular task within a workflow, not as a post-execution hook or notification mechanism tied to workflow completion. You would need to explicitly add a
WebhookTask
as the final node in your workflow and manage error handling and state propagation yourself within the workflow logic. This means catching exceptions or passing state to the
WebhookTask
as part of your workflow definition, rather than relying on Flyte to trigger it automatically on workflow completion or failure. This limitation is not specific to Azure; it is a general Flyte behavior based on the current data sources. For workflow-level notifications, Flyte's native notification system (configured in FlyteAdmin) currently supports Email, PagerDuty, and Slack, but does not natively support webhooks or Azure notification services. There is ongoing discussion and some work towards supporting more generic event sinks and webhook-based notifications, but as of now, this is not available for Azure deployments or as a general webhook trigger on workflow end-state. See the related discussion and feature requests for more context: Flyte notifications and webhooks, WebhookTask usage. Would you like more detail on how to implement a pattern for workflow-level notifications using tasks, or on the current state of webhook notification support in Flyte? Sources: - Flyte notifications and webhooks - WebhookTask usage 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.