Workflows Can Now Automatically Update Previously Posted Slack Messages

💬 Workflows Can Now Automatically Update Previously Posted Slack Messages

With Rootly’s configurable workflows, the app can automatically post to Slack when you take certain actions like updating the incident’s severity or status. We’re adding another degree of control here by allowing you to choose whether you want workflows to post a new Slack message or update a previous one. Choosing to edit previously posted messages helps you eliminate confusion from out-of-date messages in your incident Slack channel.

You can change this setting by enabling the “Replace Parent Message” option in workflows that post to Slack. With this option, Rootly will edit the previous message from the workflow instead of posting or threading a new message. When this happens, you’ll see text below the Slack message that shows that the message was automatically updated by Rootly, and at what time the last update happened. This reduces clutter in the channel and ensures responders don’t risk reading incorrect information from an outdated Slack message.

Here’s a quick video demo:

🌝 New & Improved

🆕 Retrospective are no longer locked strictly for post resolution—now they can be created and accessed during any phase of the incident
🆕 Assignees in Linear can now be automatically assigned via workflows
💅 Added the ability to auto-update incident when Jira ticket is updated
💅 Implemented guardrails to prevent non-stop loops on workflows
🐛 Fixed incorrect incident status and incident link display on Action Items metrics table
🐛 Addressed issue with cancellation messages not being logged in the incident timeline