FluxDeployDocs
Topics: Notifications

Notifications

Notification settings (/settings/notifications) control how and when FluxDeploy tells you about deployment and infrastructure events. Configuration is split across three sub-tabs.

Channels

A channel is a destination - Email, Slack, Microsoft Teams, or generic Webhook. Each channel has:

  • Name and type
  • Enabled toggle
  • Endpoint details (recipient list for Email, webhook URL for Slack/Teams/Webhook)
  • Subscribed categories - Which event groups this channel receives (Deployments, Relays, Images, Drivers, Security, System)
  • Event overrides - Opt a specific event into or out of this channel independently of its category

Status Column and Delivery Tracking

Each channel row shows a Status column reflecting the result of the most recent delivery attempt:

  • OK - Last send succeeded
  • Failed - Last send failed (the error is shown on hover)
  • Disabled - Channel turned off by the admin or auto-disabled (see below)
  • Never Sent - No delivery attempted yet

Auto-Disable on Repeated Failures

A channel that fails to deliver repeatedly is auto-disabled to prevent runaway retry loops and flooding the admin with error logs. When this happens:

  • The channel's Enabled toggle is cleared automatically
  • The Status column shows Disabled with the reason set to the last error
  • An audit log entry is written

Re-enable the channel after fixing the underlying issue (wrong webhook URL, SMTP credentials, etc.). The delivery state resets on the next successful send.

Test Button

Every channel has a Test button that sends a synthetic event. The Status column updates with the result, making it easy to verify configuration before relying on real events.

Events

The Events tab lists every event type FluxDeploy can emit, grouped by category. For each event you can toggle it globally and per-channel.

Some events are disabled by default on new installs to keep the signal-to-noise ratio reasonable:

BootImageCompleted, BootImageFailed, AutoBootImageRebuild, RelayOnline, RelayUnreachable, DeploymentStarted, DeploymentCompleted, DeploymentFailed, ServerStarted

Enable these explicitly if you want them.

The three Core update events (FluxDeploy update available / installed / failed) are on by default; see Updating FluxDeploy.

SMTP Server

Configured at the bottom of the Channels tab, below the channel list, because it is the transport the Email channel type uses rather than a separate concern. It sets the outbound mail relay:

  • Host, Port, Use TLS
  • Username / Password (password is encrypted at rest via the Data Protection API)
  • From Address and From Name
  • Test Connection button - Opens an SMTP session and reports the result

SMTP configuration is shared across all Email channels; individual channels only specify recipients.