Skip to content

Migrate from OpsGenie to Spike and never miss a critical alert.Get 20% off your first year 

← All emails

No. 23 · Oct 22, 2026 · Routing

Do you have an incident everyone ignores?

A routing rule can close it for you.

Every Tuesday at 2pm the weekly batch job triggers the same "queue depth high" incident, and someone on your team acknowledges it and moves on.

But nobody resolves it and it sits on your dashboard for days. This results in a pile of stale incidents, which makes it harder to spot the ones that actually need attention.

To clear these stale incidents, you can set up a routing rule that auto-resolves the incident a few minutes after it triggers. The batch job is done by then, so nothing is lost by closing it.

Then your dashboard only shows the incidents that still need a person, and an open one finally means something again.

Get the next one in your inbox

A weekly email for engineers who carry the pager.

Enter to open, arrows to move, Esc to close

Browse everything on spike.sh