Workflow Debugger

πŸ› Workflow Debugger We are excited to launch our Debug Workflows capability for all customers! If you've ever wondered why a workflow did not run and spent time debugging it, this is for you. This compares incident conditions against expected values against actual values and provides a pass or

Workflow Debugger
On this page

πŸ› Workflow Debugger

We are excited to launch our Debug Workflows capability for all customers!

If you’ve ever wondered why a workflow did not run and spent time debugging it, this is for you.

This compares incident conditions against expected values against actual values and provides a pass or fail result depending on what was satisfied.

  • Debug in seconds instead of manually cross checking if conditions were met
  • Drill down into specific workflows on a per incident basis
  • Used for incidents, postmortems, action items, pulse, and alert workflows
  • Support for custom field conditions

Our Workflow Debugger complements our other suite of engineering productivity tools such as Incident Variable Explorer.

What else shipped
  • πŸ†• Multi-select option on filters in Web Platform
  • πŸ†• Due date field for action items
  • πŸ†• Workflow task for adding comments to Linear tickets
  • πŸ†• Workflow task for updating Opsgenie alerts (acknowledge + close)
  • πŸ†• Incident variables for scheduled maintenance {{incident.scheduled_for}} and {{incident.scheduled_until}}
  • πŸ’… Better and human readable date filters for Rootly API
  • πŸ’… Cleaned up free trial demo data for action items
  • πŸ’… Less noisy default Form Fields on free trials
  • πŸ’… Better error messaging when free trial has ended
  • πŸ’… Removed deleted workflows from showing up in Debug Workflows
  • πŸ’… Removed confusing drop down menus from incident creation on Web Platform
  • πŸ’… Default 90 day filter for metrics
  • πŸ’… Updated customer logos on Rootly
  • πŸ› Fixed issue where canceling the creation of a workflow via template gave a 404 error
  • πŸ› Fixed issue where some redirect links for integrations gave a 500 error
  • πŸ› Fixed issue where services and teams updated trigger were not firing properly

_Editor’s note: Atlassian is retiring Opsgenie, with end-of-life scheduled for April 2027β€”factor a migration path into any evaluation._

Your privacy choices

Rootly uses cookies from advertising partners to measure our ads and to show ads for Rootly on other sites. Some US state laws call that selling or sharing personal information. You can opt out of it for this browser here.

Analytics we use to improve this site stay on. Read Rootly's Privacy policy for more information.