Overview
Every trigger has a schedule that controls when its notifications are delivered. Alius supports five schedule options: one immediate and four batched.Schedule Options
| Schedule | Behavior |
|---|---|
| Instant | Notification is sent immediately when the trigger fires |
| Hourly | Events are batched; one notification is sent once per hour |
| Daily | Events are batched; one notification is sent once per day |
| Weekly | Events are batched; one notification is sent once per week |
| Monthly | Events are batched; one notification is sent once per month |
Instant
Instant is the default schedule. The notification is dispatched as soon as the webhook is processed and conditions are met. There is no delay or batching. Use instant when you need to act on events as they happen — for example, high-value orders, low stock alerts, or abandoned cart recovery.Batched Schedules (Hourly / Daily / Weekly / Monthly)
When a batched schedule is selected, Alius stores each matching event as a Scheduled Notification rather than sending it immediately. At the end of each scheduled interval, the worker collects all pending notifications for that trigger and sends a single consolidated message.What a batched notification contains
Each batched notification includes the message content from the most recent event in the batch window. The batch is cleared after sending.Batched notifications in History
Pending batched notifications appear in Notification History with a status of Scheduled until they are sent. Once sent, the status changes to Sent.When to use batched schedules
| Schedule | Use case |
|---|---|
| Hourly | Frequent events where per-event noise is too high (e.g., product updates during a bulk import) |
| Daily | End-of-day summaries — daily order counts, new customer signups |
| Weekly | Weekly digest reports — inventory changes, return summaries |
| Monthly | Monthly business reviews — aggregate order or customer metrics |