Notifications & Alerts

​

Automatic alerts

​

Grouping and deduplication

• The first failure of an agent notifies immediately.
• Subsequent failures of the same agent and type within a 15-minute window increment the same notification (“12 failures in the last 15 min”) instead of creating new ones.
• Each execution is counted once, even when detected by more than one path.
• Within a group, severity only escalates (a critical event upgrades a warning group, never the opposite).

​

Custom alerts from the SDK

import { sendNotification } from '@runflow-ai/sdk';

// Simple warning (default severity)
sendNotification('Customer record missing in CRM');

// Critical alert with details
sendNotification('Stock depleted in ERP', {
  severity: 'critical',
  body: `SKU ${sku} returned zero availability during order flow`,
});

// Deduplicate by your own key: the same document only alerts once per execution
sendNotification('Invoice validation failed', {
  severity: 'warning',
  dedupeKey: invoiceId,
});

​

Options

​

Behavior

• Fire-and-forget — sendNotification() never throws and never blocks your agent’s execution.
• The alert title you pass becomes the notification title in the portal, grouped per agent like automatic alerts.
• Custom alerts appear with the type Alert in the bell and history filters.

​

Where notifications surface

​

Health metrics

• Executions and failures per agent (combining the trace layer with the execution store of record)
• Error rate with health classification: healthy (<5%), degraded (5–20%), critical (≥20%)
• Timeouts and stuck executions
• Connector failures per agent
• Most common errors, grouped by normalized message (IDs and numbers collapsed so identical failures group together)