Back to roadmap
US-1042

Real-Time Notifications

HIGHIN PROGRESS
Agent working · step 3 of 7Last verified 4 min ago
User story
Comments · 1
SCSarah Chen· 2h ago

“respond immediately”

What's our definition of a “critical” event here? Want to make sure the SLO matches.

Architect
real-timewebsocketfan-out
Channels & integrations · auto-detected from this story
In-appSEmailTSMSSSlack
Provider required
Add a push provider for mobile alerts
O
OneSignal
Recommended
ConnectView all
approved
Notification toast
updated 2d ago
Open
in review
Reconnecting state
updated 4h ago
Open
draft
Preferences panel
updated 1d ago
Open
Scenario 1: User receives notification on a critical event Verified
Givena user is logged into the platform
Andthey have notification preferences enabled
Whena critical event occurs in their workspace
Thena real-time notification appears within 2 seconds
Andthe notification contains event type, timestamp, and source
Comments
Scenario 2: Notification respects user preferences Verified
Givena user has disabled email notifications
Whena critical event triggers a notification
Thenonly in-app and push notifications are sent
Andno email is dispatched
Comments
Scenario 3: Fails gracefully on WebSocket disconnect Failing
Givena user's WebSocket connection drops
Whena critical event occurs
Thenthe notification is queued for retry
Andthe user sees a reconnecting indicator
Andqueued notifications are delivered on reconnect
QA agentPlaywright· ran 4 min agoView run
Expected queued notifications delivered within 5s of reconnect · Actual: 0 delivered after 12s
Likely cause: Retry & Fallback Flow
Comments