ISA-18.2 alarms: three priorities with their own shape, colour and words, acknowledge and clear states, and a sorted list that announces new alarms to screen readers.
Alarm priorities
Install
npx shadcn add @syncrobotic/alarm Also installs: lucide-react, @syncrobotic/cn, @syncrobotic/use-presence, @syncrobotic/feedback, @syncrobotic/robot-icons
Overview
Alarms after ISA-18.2: three priorities, each with its own shape, colour and words, acknowledge and clear states, and a sorted list that announces new alarms.
More examples
States and real uses. Each example is also a Storybook story and a visual regression test.
Alarm states
Alarm with action
Alarm list sorted
Alarm list shelved
Alarm list flood
Alarm list loading
Alarm list error
Usage rules
- Only for an abnormal condition that needs an operator to act. No action, no alarm: log it instead.
- Three priorities, each with its own shape, colour and word: critical (act now), high (act within minutes), low (act when convenient).
- Stays until the condition clears and someone acknowledges it. Acknowledging records that it was seen; it does not clear it.
- Never auto-dismissed, never a toast, never blinking, never a tinted row. Colour is only on the glyph and the priority word. Unacknowledged: bold title and a solid bar in the priority's colour. Cleared but not acknowledged: still bold, the bar dashed, and it says when it cleared. Acknowledged: regular and grey, with when (“Acknowledged 13:42”, from
acknowledgedAt). - Time comes first, in tabular figures, so order and age read down the column. Below 576 px of width the row reflows: the time under the title, the state and buttons on a line of their own.
- “Acknowledge all” appears only when the app passes onAcknowledgeAll, with two or more alarms it may take in view, and takes only those: never a critical alarm (each is acknowledged on its own row; the button then reads “Acknowledge 3 non-critical”), never shelved, suppressed or out-of-service alarms, and in a flood the folded low ones only while their group is open (“Acknowledge 2 shown”). Screen readers hear how many were acknowledged. Leave it out where every alarm must be read on its own.
- One alarm per root cause. If the robot is offline, do not also raise camera lost and lidar lost.
- Shelving hides a nuisance alarm for a set time and it comes back on its own; it is never permanent and never for critical alarms. Suppressed by design (the app's logic) and out of service (maintenance) are counted under the list, not hidden silently.
- Pass
raisedAtso a flood (over 10 alarms in 10 minutes) is named and the low ones fold away; then fix the root cause the flood points to.
Changelog
- 0.27.02026-11-21Buttons beside Acknowledge (a custom action, Shelve) are ghost, so Acknowledge is the only outlined button in an unacknowledged row. Unshelve, alone in its row, keeps its outline.
- 0.22.22026-11-20"Acknowledge all" appears only when
onAcknowledgeAllis passed (no longer fromonAcknowledgealone), and never takes a critical alarm: each is acknowledged on its own row, and while one is unacknowledged the button reads "Acknowledge 3 non-critical" (labelacknowledgeNonCritical). - 0.22.12026-11-20Low priority is a diamond (
DiamondAlert), not a circle: at 20 px the circle read as the critical octagon. AlarmList takesstatus("loading" shows placeholder rows and never "No active alarms"; "error" says the list could not load or update, keeps what it has, withonRetryandupdatedAt). Labelsloading,errorEmpty,errorStale,updatedAt,retry.useAlarmSignalstakesready: alarms that arrive with the first load do not buzz.