Notifications
RedStick AI provides real-time notifications for execution events, team activity, and action items.
Notification Delivery#
Notifications are delivered through two channels:
- Real-time WebSocket — Instant push to the browser
- Email digests — Periodic email summaries of unread notifications
Notification Types#
This list reflects events that actually fire. Some historical event types in the API are reserved but unused.
Execution Lifecycle Events#
- Task started (
task_started) — An execution has begun - Task completed (
task_completed) — The worker finished its task successfully - Task failed (
task_failed) — The worker encountered a non-infrastructure error - Task timed out (
task_timed_out) — An execution exceeded its time limit - Session crashed (
session_crashed) — An infrastructure failure forced an execution to abort. Thesession_*naming is historical; this event refers to a single execution. - Session resumed (
session_resumed) — An execution was retried after a previous failure or cancel
Billing Events#
- Overage budget warning (
overage_budget_warning) — Your compute-minute usage is approaching the overage budget you've set - Overage budget exceeded (
overage_budget_exceeded) — Your compute-minute usage has reached or crossed the overage budget
Notification Center#
Access the notification center from the sidebar:
- Unread count badge shows pending notifications
- Action required summary highlights items needing your attention
- Thread view — Related notifications are grouped into threads
- Mark as read — Mark individual or bulk notifications as read
- Dismiss — Remove notifications you've handled
Preferences#
Customize notification behavior from Notification Preferences:
- Enable/disable notifications per channel
- Control which event types trigger notifications
- Configure email digest frequency
Email Digests#
The platform sends periodic email digests summarizing unread notifications. The digest sender runs as a background task and batches notifications to avoid excessive emails.
Retention#
Old notifications are automatically pruned by the retention pruner background task. This keeps the notification list manageable and the database clean.