Alerts Dashboard & Acknowledgement

Available from: v1.0.63

The Direct Debit service monitors configurable thresholds — mandate creation rate, daily and weekly collection amounts, and clawback reserve levels — and raises alerts when those thresholds are breached. Starting in v1.0.63, all alerts are surfaced through a dedicated dashboard page with full acknowledgement support.

---

Alerts Dashboard

Route: /dashboard/alerts

The page presents a unified list of every alert the service has ever raised, split visually between active (unacknowledged) and historical (acknowledged) entries. For each alert the following fields are displayed:

Field	Description
Type	The alert category (e.g. mandate_creation_rate, daily_collection_amount, clawback_reserve_low)
Severity	The severity level attached to the threshold configuration
Triggered value	The actual measured value at the time the alert fired
Threshold	The configured limit that was exceeded
Timestamp	The UTC date/time when the alert was raised

Active alerts are highlighted so they are immediately distinguishable from resolved history.

---

Acknowledging Alerts

Acknowledging an alert marks it as resolved. The system records:

• Acknowledged at — UTC timestamp of the acknowledgement action
• Acknowledged by — the username of the user who performed the action

Single Acknowledgement

Click the Acknowledge button on any active alert row. The alert immediately transitions to the historical list with its resolution metadata.

Bulk Acknowledgement

Select multiple active alerts using the row checkboxes and use the bulk action control to acknowledge all selected alerts in one operation. This is useful after an incident where several related alerts have fired.

---

Sidebar Badge

The sidebar navigation includes a badge on the Alerts link that shows the current count of active (unacknowledged) alerts. The count updates to reflect the live state, so team members can see at a glance whether action is needed without visiting the alerts page.

---

API-Driven Acknowledgement

For integrations (such as agentOS), alert acknowledgement is also available via a tRPC procedure. This allows external systems to acknowledge alerts programmatically and keep acknowledgement state in sync across tools.

tRPC procedure

// Acknowledge a single alert
alerts.acknowledge({ alertId: string, acknowledgedBy: string })

// Acknowledge multiple alerts
alerts.acknowledgeBulk({ alertIds: string[], acknowledgedBy: string })

Both procedures return the updated alert record(s) including acknowledgedAt and acknowledgedBy.

Note: The exact procedure names and signatures should be confirmed from your tRPC router definition. The examples above illustrate the intended shape.

---

Alert Types Reference

Alerts are raised by the threshold monitoring system when the following conditions are breached:

Alert type	Trigger condition
mandate_creation_rate	More than the configured number of mandates created within a rolling hour
daily_collection_amount	Daily new DD collection total exceeds the configured limit
weekly_collection_amount	Weekly collection total exceeds the configured limit
clawback_reserve_low	Clawback reserve in the Griffin holding account drops below the configured minimum

Thresholds are configured per customer (letting agent) so each agent's alerting is scoped to their own activity.