# Preview routing

> See exactly what your rules would do with an event, live, without sending or storing anything.

Web page: https://infrainbox.app/docs/notifications/test-an-event/

Open **Notifications › Preview routing** (dashboard screen `/rules/dry-run`), or click **Preview routing** wherever you are: Routing, a rule's or a built-in rule's editor, a source, an incident or an event. Outside the tab it opens in a drawer on the right, over the rule or page you're already looking at, and each entry point brings its context: from a source you start on a sample from that source, from an event or an incident with that event already chosen. Otherwise the newest event is chosen for you, so **Run** works straight away. From a rule's editor it tests your **unsaved edit** in that rule's place, so you can check a change before you save it. From a built-in rule it tests the saved built-in rules: apply and save the edit first.

Nothing here is sent, nothing is stored, no incident moves, and no rule version changes. Run it as many times as you're editing.

## Picking what to try

Either:

- **A recent event** — pick one from the compact, searchable list beside **Preview routing**, and it's run through the rules exactly as it originally would have been. The line underneath confirms which one: its title, severity, source and when it arrived.
- **A sample you compose** — pick the source; the title and severity (Critical through Debug) prefill with a realistic example for its integration (a Proxmox backup failure, a Kuma monitor down, and so on), which you can edit. Type, resource, dedup key, tags and body sit under **Customize sample**, folded away until you need them.

With no recent events yet, it opens on a sample by itself, so there's always something to run.

## Reading the answer

The answer appears right below and scrolls into view as soon as it's ready, with a screen-reader announcement — nothing to hunt for after clicking **Preview routing**.

The answer is one line, under **Simulation · nothing is sent**: what happens to the event and who is notified, for example "Saved in History · no incident · Telegram and Phones notified", "Opens an incident · Home alerts held back by quiet hours" or "Dropped · nobody notified". The next line says what decided: **Decided by** your rule, a built-in rule, a rule for some sources or Default. An event kept in History still notifies the recipients its rule names, with a one-off message each. The test reads your workspace's actual silences, quiet hours and destinations live, so a message they would hold back shows as held back.

**Details** holds the rest:

- **Messages it would send** — one line per destination, and whether it would go out or be held back, and until when.
- **Rules checked, in order** — matched, matched and continued, or didn't match.
- The kind of event, its severity, the route, what happens to the incident, why nobody is told when nobody is, the gates that hold messages back, and the tags.

A recovery or a resolve always shows what it would resolve, even when the rule it matched routes to `drop` — ending an incident isn't optional the way opening one is.

## Why it needs admin or owner

Running it needs to be limited to whoever can already see the workspace's destinations, quiet hours and silences, since the answer shows all three. A member sees a short note saying so instead of a form they can't run, and can still read the rules themselves.

## Next

- [Routing rules](https://infrainbox.app/docs/notifications/routing.md) — what you're testing
- [Coverage](https://infrainbox.app/docs/notifications/routing.md#seeing-what-actually-happens) — the same idea, one severity at a time, for every destination at once
