---
title: 8. Alerting
slug: lf-lab/8-alerting
docTags: 
createdAt: 2026-05-19T07:55:06.114Z
---

### Narrative context

A journey running at scale will fail occasionally — an external endpoint times out, an audience evaluation falls behind, a decision policy hits an unexpected null. Without alerting, those failures are discovered when a customer complains. With alerting, the operations team knows within minutes and can decide whether to intervene.

### Subscribe for alerts

In the left menu, click **Administration → Alerts.**

Here you can find the list of predefined **Alerts**. You can find two type of alerts:

- Channel configuration related.
- Journey related.

If you want to subscribe to a specific alert:

- click on the three-dots icon :inlineImage[]{src="https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/BXuvViRUOH7wYRzSkMK8C-20260520-163943.jpg" alt caption width="43" height="43"} beside the title.
- Click **Subscribe**.
   From now on you'll received an email every time the alert is triggered.

:::hint{type="info"}
You can also subscribe via **I/O Event** notifications, which allows integration with external systems.
:::

### CJA as the other alerting surface

AJO operational alerts answer the question *"is the platform working?"*. They are tuned for the engineer or operations lead.

CJA scheduled alerts answer *"is the marketing performing?"*. They are tuned for the marketer or the campaign owner. You will build one later.

### Business punchline

You have placed a quiet sentinel beside the journey. If something breaks at 3 AM, somebody will know soon. The customer-facing experience is protected not by hope but by an explicit promise to detect problems as soon as possible. Production operations becomes a routine, not a panic.