Blog
Insights & updates from our experts
Automation rules can save a lot of time, and even mistakes, by automating predictable events in Xurrent, or events that occur often. In some cases, these automation rules can become quite long, containing multiple expressions and actions. Keeping such complex automation rules orderly makes it easier to properly maintain them. This has now been improved, by making it possible to easily change the order of the actions of a rule.
When an account administrator or designer hovers the mouse pointer over any of the actions of an automation rule, a subtle ‘grabber’ appears at the far left of the line, just left of the note, value, or email icon. Hovering the mouse pointer over it, the pointer changes to the ‘move’ pointer.
Just by dragging this line to another position within the actions, the order of the actions can now be changed at will.
It was already possible to change the order of the automation rule expressions this way. These expressions should, of course, not be rearranged just to group them in a more readable way, as the order in which they are placed dictates the processing order.
Incident Management
An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.
5 Mins
September 10, 2026
Incident Management
