Set Routing Priority With Drag-and-Drop Order
Control the exact sequence All Quiet uses to evaluate incident routings. Drag rules up or down in your Routing list to run high-priority automations before general routing logic.
Published: Tuesday, 11 August 2026
Custom routing order lets you control the exact sequence All Quiet uses to evaluate incident routings. By prioritizing specific rules, you guarantee predictable incident automation and ensure your teams receive only critical alerts.
Key Benefits and Details
| Feature | Description |
|---|---|
| Primary Goal | Run high-priority automations before general routing logic. |
| Availability | Users with edit access to all routings in the current list. |
| Location | Routing list (use the drag handle on the left). |
How It Works
- Navigate to your Routing list.
- Click and hold the drag handle on the left side of a routing.
- Drag the routing up or down to set its priority.
- Release the handle. The system saves the order automatically.
- All Quiet processes these routings from top to bottom instead of alphabetically.
- Routings without a custom position appear after your ordered list, sorted by name.
Limitations and Security
To maintain reliable alert flows:
- You need more than one routing to reorder the list.
- You need edit access to every routing present in the view.
- You cannot reorder provisioned routings.
More updates
-
New
Terraform Provider Version 3.1.0: Granular Security and Configuration
All Quiet Terraform Provider v3.1.0 adds inbound webhook security, dynamic Slack channels, status page privacy controls, routing uptime exclusions, and incident engagement report settings.
-
New
Snooze Similar Incidents To Suppress Repeat Alerts
When you snooze an incident, you can now automatically snooze future incidents that match the same conditions. All Quiet creates a team routing rule so noisy integrations stop paging your team repeatedly.
Updated August 11, 2026