🔄 Reordering Escalation Paths

Managing incidents effectively requires flexibility in how escalation paths are evaluated. By setting an order for Escalation Paths, you now have the power to structure your escalation logic exactly how you need it.

What’s New:

• Customizable Order: Manually reorder the escalation paths within an escalation policy to create an IF, IF-ELSE, and ELSE logic. Prioritize paths based on your team’s workflow and response needs.
• Improved Flexibility: Previously, escalation paths were executed in the order they were created while still checking against conditions. Now, you decide the sequence in which paths are evaluated.
• Seamless Transition: Existing policies have been automatically converted to the new format, so you can start reordering today.

Why It Matters:

This enhancement gives you greater control over how incidents are escalated, ensuring the right people are notified at the right time and reducing delays in your response process.

For example, if a critical database alert is triggered, you could set it to immediately notify your on-call DBA team. If no acknowledgment is received within five minutes, the alert could escalate to a senior engineer or an SRE. On the other hand, a less urgent alert—such as a non-critical system health check—could follow a different escalation path, ensuring the right expertise is brought in at the right time.

How It Works:

1. Navigate to your escalation policy in On-Call > Escalation Policies.
2. Drag and drop the escalation paths to reorder them.
3. Save your changes, and Rootly will evaluate the paths in your specified order.

With this added control and flexibility, your team can create tailored escalation paths to handle incidents more efficiently. Start reordering your escalation paths today!

🌝 New & Improved

🆕 Added the ability to run recurring workflows indefinitely, even if run conditions are no longer true. This is a great way to configure inactivity reminders where you continue to poll the incident channel for activities until the channel is archived.

💅 Updated Incident Retrospective API to return additional data about the each incident retrospectives and its step details. Previously, these details were only accessible via web UI.

💅 Added soft deletion logic to ensure deletion of custom fields will NOT impact historical data. Previously, only selection of built-in fields will persist on historical data. Now, custom field selections will persist as well.

💅 Rootly On-Call alert volume can now be adjusted in-app for both iOS and Android. Users no longer have to rely solely on the sound settings native to the mobile devices.

🐛 Fixed intermittent issue with Alert Urgency permission settings not persisting.

🐛 Fixed issue with + Add Condition button becoming disabled in workflow editors when selecting from filtered list of conditions.