Skip to content

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

← All emails

No. 17 · Aug 27, 2026 · Routing

Why some critical incidents land quietly in Slack?

Even when your routing setup works perfectly fine.

Say your routing rule reads the incident payload and looks for a field called customer_type. If the value is enterprise, the rule triggers a phone call, and anything else gets a Slack message.

That works fine until the monitoring tool pushes an update and renames the field to customer_plan. The rule doesn't notice and quietly stops matching.

Every incident now defaults to Slack, enterprise included. Your highest-paying customer waits on a Slack notification, not a phone call.

The gap can go unnoticed for weeks. It surfaces when someone reviewing the queue spots an enterprise customer incident that never triggered a call and traces it back to the renamed field.

A renamed field is one blind spot that lets critical incidents slip through a routing rule unnoticed.

Our guide covers other blind spots like this, so you can catch them before they cost you a response.

See all 3 routing blind spots →

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