Notification History

View, filter, and search all notification delivery records

Overview

The History page shows a log of every notification Alius has attempted to send. Each entry records what was sent, when, to which hub and recipient, and whether it succeeded.

---

Notification Statuses

Status	Description
Sent	The notification was delivered successfully
Failed	The delivery attempt failed (see the error message on the entry)
Scheduled	A batched notification is pending its send window (see Schedule Types)

---

Log Entry Fields

Each entry in the history log contains:

Field	Description
Trigger title	The name of the trigger that fired
Trigger type	The event type (e.g., order created, product updated)
Hub	The notification hub used: Slack, Email, or Telegram
Recipient	The specific channel, email address, or Telegram chat
Message preview	A short preview of the notification content
Timestamp	When the notification was created
Error message	Populated only for Failed entries — the error returned by the hub

---

Filtering

The history log can be filtered along three dimensions simultaneously:

Filter	Options
Status	All · Sent · Failed · Scheduled
Type	All · Products · Orders · Customers · Returns · Cart
Search	Free-text search on trigger title

Filters are applied in combination — for example, you can search for failed notifications from order triggers.

---

Sorting

Results can be sorted by:

• Date (newest first by default)
• Hub (Slack / Email / Telegram)
• Status

---

Pagination

The history log displays 25 entries per page by default. Use the pagination controls at the bottom of the page to navigate through older records.

---

Failed Notifications

When a notification fails, the entry’s error message field shows the reason returned by the hub (e.g., invalid token, channel not found, rate limit exceeded). Use this to diagnose delivery issues with your integration.

Common causes:

• Slack: Bot token revoked or bot removed from channel
• Email: Recipient address bounced or recipient is inactive
• Telegram: Chat ID no longer valid, or repeated rate-limit failures after retries exhausted