Alert Status and Notification Reference

This page is the short operational reference for people who work with alerts in the product.

Alert status matrix

Status	What it means in practice	Visible for	Typical next action
`alerted`	the issue is currently open and should be reviewed	user, admin, superadmin	review or acknowledge
`acknowledged`	someone has seen the alert and accepted ownership	user, admin, superadmin	continue work, monitor outcome
`outdated`	an older alert row was replaced by a newer one	mainly admin and deeper review	usually read-only historical context

Alert type	What users usually see	Typical example
Message alert	failed or unusual message behavior	repeated message failures
iFlow alert	deployment or artifact problem	iFlow error state
Keystore alert	certificate timing problem	expiring certificate
Daily no-message alert	expected traffic did not happen	one integration stayed silent

Channel	What it is used for	Example
`email`	direct delivery to an owner or support group	SMTP-based alert mail
`ui`	in-app operational visibility	alert list and overview cards

Current product behavior is primarily email plus UI visibility.

Acknowledging an alert means the issue has been seen and taken over. It does not automatically solve the underlying problem.

Suppression reduces repeated noise for a defined period. Use it when the signal is known and repeated reminders add no value for a while.

Because the technical condition may still exist. The state changed, but the cause may still need action.

See: