Critical findings and notifications
Inspect configured findings, choose authorized recipients, and understand delivery receipts.
Watch the workflow: Preview notification scope and replay controls · Authored dummy data
This authored walkthrough uses the earlier Alerts layout. Open new rules in Settings → Notifications in the current app. In the recording, name the unsaved demo configuration and review its stored-failure condition, scoped demo customer, recipient and channel. Expand the historical-replay controls while leaving Notify about past findings unchecked. This form is not saved, no rule is activated and no notification is sent. The authored demo check does not establish an approved evaluation or delivered alert.
Read the walkthrough transcript
- 00:00 — Prepare a notification rule in Tensile using the authored demo check.
- 00:05 — Review its recipient, channel and replay limits. This form is not saved.
Select the bell beside the workspace name to open triggered alerts in the sidebar. Each alert opens its exact delivery record. Failed delivery remains visible; there is no unread dot or count in this version. Select Back or press Escape to return to navigation.
Open Settings → Notifications to configure rules. Select Delivery history to inspect critical findings and their recorded assessments. An evaluator failure does not establish a customer-confirmed error or business outcome. Those remain Unknown until supported by separate evidence. Trace votes retain their own label and do not establish customer authorship.
Configure a notification
Notification rules appear in a table, with an empty state when none are saved. Workspace owners and admins can choose New notification rule in Notifications to open a creation dialog, select a stored check and customer scope, and choose a workspace recipient and channel. Saving creates a versioned critical condition for recorded failures. It does not confirm delivery.
Slack DM requires this workspace’s saved Slack connection and verified recipient mapping. Email requires configured delivery and an authorized recipient. Ask your workspace administrator or delivery operator to establish missing setup. Historical replay is off by default; enabling it can send multiple messages.
Inspect and recover
Select a finding to open its underlying trace, assessment and delivery receipt. A Skipped receipt means the last attempt sent no message. A provider acknowledgement is separate from inbox arrival or customer confirmation. Missing or stale worker checks leave current availability unknown.
Use Review delivery to inspect a setup failure. After confirming repair, an owner or admin can request a bounded retry. Each finding allows at most three dispatch attempts, including setup skips. An ambiguous receipt requires checking the channel because retry may deliver a duplicate. Paused rules cannot retry.
Send test queues a synthetic own-recipient test; it does not evaluate customer work. Check the resulting receipt before attempting another send. Duplicate findings and corrections remain deduplicated while their history is retained.
Existing Alerts links
The separate Alerts navigation entry is retired. Existing /alerts links open Settings → Notifications. Links to a finding open that exact full-page delivery record, including older receipts outside the latest 200 rows. Missing or unauthorized records stay unavailable. Return through the Delivery history breadcrumb to restore its search, sort and page. Existing scheduled rules retain their condition, schedule, lookback and enabled state in Notifications.