Monitoring and alerts
Find out when a journey breaks, once, where your team looks
Monitoring re-runs a flow on an interval against the environment it was switched on for. Alerts go out when something changes, not on every run.
Monitoring
Choose an interval in the top bar. The scheduler re-runs the flow and records pass rate and p50 and p95 duration. The shortest interval and the number of monitored flows depend on the plan: Personal every 5 minutes, Team every minute and Business every 30 seconds. Runs from monitoring don’t count towards a plan’s monthly flow runs.
Alert channels
| Channel | How |
|---|---|
| Up to 10 addresses per channel. A new address confirms through a link before alerts reach it; people with an account in the organization are confirmed at once. | |
| Microsoft Teams | A Workflows or incoming webhook; Journey Lanes posts an Adaptive Card. |
| Slack | An incoming webhook. |
| Webhook | A JSON POST over https with event set to flow.failing, flow.recovered, flow.test, flow.drift or flow.sign-in. |
Webhook URLs are stored encrypted and only ever shown as their host. “Send test” checks a channel, and every alert’s history, with delivery results per channel, is on the same screen.
When alerts go out
- Failing: when a flow has failed a set number of monitor runs in a row (1 to 5, default 2), every enabled channel gets one alert naming the failing step and the failed checks, with a link to the flow.
- Recovered: one more alert when it passes again. Nothing is sent in between.
- API changes: one alert when the daily rescan finds that steps of monitored flows lost their endpoint.
- Saved sign-ins: one alert when a pasted refresh token is refused, until a new one is pasted.
Monitor the journey that matters most
Switch on monitoring and choose where the alert goes.