Alert history and notifications
The Alerts page and the bell record every fire in the workspace. Browser push and email tell you when a rule fires or when a run or a Jason task finishes.
Every alert that fires in a workspace is recorded once, whatever channel it went to. You can read them in three places: the Alerts page, the bell in the top bar, and the channel you attached to the rule. On top of rules, you can ask to be told when a specific run or a specific Jason task finishes.
The Alerts page
Open it from the bell’s View all link or from Manage alert rules on the rules page. Its address is /notifications/history.
Each row shows:
Clicking a row goes to the most useful place: the run for run alerts, the page the alert points at otherwise. Pages are 50 rows long with Previous / Next and a per-page selector at the bottom. There are no filters; use a rule’s own History tab to see one rule’s fires, including the evaluations that did not trigger. See Alert rules.
Header actions:
Empty state: “No alerts to show — New alerts will appear here when a rule fires or watched work finishes.”
Clear all
Clear all on the Alerts page, or in the bell, hides everything currently listed. It is worth knowing exactly what it does:
There is no per-item dismiss or delete, and no retry for a failed delivery.
The bell
The bell sits in the top bar of every page, next to the share icon.
The bell refreshes every few seconds and when you return to the tab, so a fire shows within moments. The sidebar’s Alert Rules item never shows a badge: badges are for active work (running chats and runs), not for configured rules.
Browser push
Push notifications reach you on your desktop or phone even when Jsonify is closed. They are a channel like Slack or email, with one difference: a push channel is bound to the person who enabled it and only pings that person’s devices.
Enabling push
- Open Integrations and choose Browser push.
- Press Enable on this device. Your browser asks for permission to show notifications; allow it. The toast reads “This device will now receive browser notifications.”
- Repeat on each device you want pinged. The card reads “This device is subscribed. Re-enable on any other browser you want pinged.” once done.
If the card says “This browser can’t receive push notifications, or the server isn’t configured for it.”, that browser does not support push (some in-app browsers and older Safari versions) — try another.
Once enabled, attach the Browser push channel to any alert rule as its channel, and rules deliver as an OS notification: the rule name as the title, the reason as the body, and a click that opens the run or page.
Because a push channel belongs to one person, a workspace rule attached to it notifies only that person. For a team, use Slack or email as the rule’s channel and let each person enable push for their own “notify me when done” pings.
If you blocked notifications by mistake, the bell on a run shows a crossed-out icon with “Notifications are blocked for this site. Enable them in your browser settings to be pinged when this finishes.” Re-allow the site in your browser and try again.
“Notify me when done” on a run
On a run that is still going, the header shows a small bell with the tooltip Notify me when this finishes. Press it, allow notifications if asked, and the toast reads “I’ll notify you when this finishes — you can close the tab.” Press it again to stop. When the run completes, fails or is cancelled you get one push with “Pipeline run finished” and, for example, “Price & promotion tracking finished — 1,204 rows.” Clicking it opens the run. Several pings about one run collapse into one notification.
“Notify me” on a Jason task
While Jason is working in the sidebar or a chat, the activity status shows Notify me. Press it to be told when the turn ends. If push is available it is used; otherwise, or by choosing (edit), a Notify me by menu lets you pick Browser push or any live Slack, email or webhook channel in the workspace, or None to stop. The ping reads “Jason finished”, “Jason replied”, “Jason needs your attention” or “Jason stopped”, with the chat title, and opens the chat.
Email delivery
Email is a notification channel like the others. Every workspace starts with an Email notifications channel addressed to the workspace owner, so a new rule can deliver by email with no set-up; add more email channels for other recipients on the Integrations page.
An alert email has the subject “[Jsonify] {rule name}”, a kicker of Run update, Jason update or Notification, the reason as the message, and a button (View run, Open task or View notification) that opens the right page. The footer says the message was sent automatically. See Slack and email.
Newsletters are emailed separately and do not appear in alert history. See Newsletters.
Completion pings
“Notify me when done” requests are delivered through a system rule named Completion pings (“Notifications you asked to receive when work finishes.”). It does not appear on the Alert Rules page and cannot be edited, but its fires appear in the bell and on the Alerts page like any other, so you have a record of the runs and tasks you asked about. Each request is one-shot: it is consumed by the first delivery.
Delivery status
Every fire records how delivery went:
| Status | Meaning |
|---|---|
| sent | The channel accepted it. |
| failed | The channel rejected it or could not be reached; the error is on the badge in history and on the rule’s History tab. Nothing is retried. |
| skipped | Nothing to send: a dry run, an evaluation that did not trigger, or push with no enabled devices. |
| logged | The rule has no channel; the fire is in-app only. |
A not delivered badge with “Integration … is not live” means the channel was disconnected or failed its last test. Open Integrations, fix or reconnect it, and use Send test on the rule to confirm.
Which alerts fired overnight, and did any of them fail to reach Slack?
Jason lists the fires since yesterday evening by rule and severity, flags the ones with a failed delivery and the error text, and offers to re-test the Slack channel.