Skip to content

Troubleshooting

My event isn't firing at all

In order of likelihood:

  1. Is it active? Check the event's active flag directly. Created with the active flag set to false and never turned on, or inactivated later — either way, dispatch skips it entirely, regardless of severity.
  2. Does the check have a threshold or evaluator at all? See Before You Start — no threshold means the confirmed severity is permanently not_evaluable, which never satisfies any floor.
  3. Is the check actually breaching at or above the floor, and is this a genuine transition? If it's been breaching for several runs already, that's expected silence — see Transition-Only. Check the evaluation history directly for that check, most recent first, to confirm what's actually happened.
  4. Did you just activate the event while the check was already breaching? That's the documented non-retroactive case in Managing Events — it'll fire on the next real transition, not immediately.
  5. For 'notify' events: is anything actually listening on that exact channel name, in a session that's still connected? An unheard notification isn't an error and leaves no trace.
  6. For 'function' events: check your logs for a warning mentioning the event's identifier — the function may be firing and failing. Dispatch never lets that abort the run, so a failing function event is easy to miss if nothing is watching for warnings.

My event fired more than once for what looks like one breach

Confirm it's genuinely re-firing, and not two different events — for example, a warning-floor event and a critical-floor event both registered on the same check will both fire, independently, as severity climbs through both floors during one worsening trend. That's two events each doing their job, not one event double-firing.

Continue to Worked Walkthrough.