> ## Documentation Index > Fetch the complete documentation index at: https://docs.meetdoris.com/llms.txt > Use this file to discover all available pages before exploring further. # Sentinel signal fired > Runs when Sentinel raises or materially escalates a flag on a deal. **Event id:** `sentinel.signal_fired` Sentinel is the layer that watches deals for anomalies. This trigger lets a flow react the moment Sentinel raises its hand. ## When it fires On a material change to a flag, which means one of three things: a new flag was raised, a flag that had been resolved came back, or an existing flag's severity moved up meaningfully. It deliberately does not fire on every recalculation. A flag that stays at the same level from one check to the next produces nothing. ## What the flow receives * **Signal** — Which signal fired, by name * **Severity** — How serious Sentinel rates it * **Deal** — The deal the flag sits on, expandable into full deal context * **Entity** — The record the flag attaches to, when it is narrower than the deal ## Good uses * Notify the deal owner with the evidence behind the flag, not just the flag * Escalate high-severity flags on large deals straight to a manager * Write a card onto the deal explaining what changed and what to do about it * Post the flag into a channel where the team already reviews pipeline ## Things to know * Add a **Continue if** on the signal name to build a flow for one specific signal, and on severity to keep it to the ones worth interrupting someone for. * Sentinel signals are governed. A signal has to pass certification before it fires at all, so this trigger is quieter than most. * Signals are configured per workspace. If a signal is not enabled for you, a flow that filters on it will never run. * A reaction flow runs as the deal owner, so anything it reads is scoped to what that person can see. Do not build one flow that reacts to every signal. Build a flow per signal you actually want a response to, each with the response that signal deserves.