Overview
The Automations view now offers new sorting options and more complete timestamps, giving you fast control over how you see your process automations and making it easy to spot what changed recently.
What's new?
- New sorting options: sort your automations by "Last Updated" or "Oldest Updated" right inside the Automations view.
- Clearer timestamps: the "Last Updated" timestamp now shows the year alongside the day and month, for an accurate and complete timeline.
How does this help?
- Fast diagnosis when something stops working: if an automation stops running, sort by "Last Updated" and instantly see whether a recent change might have caused the behavior.
- Precise timeline reading: with the year in the timestamp, you know exactly when each automation was changed, with no ambiguity across different years.
- Immediate view of recent activity: sorting arranges your automations by their latest edit, giving you a clear snapshot of what was touched most recently.
Use cases
1. A Pipe Admin investigating an automation that stopped firing. A card didn't advance to the approval phase as it should have. The admin opens the Automations view, sorts by "Last Updated", and sees that the movement automation was edited two days earlier. They pinpoint the recent change as the likely cause and fix the rule without auditing automation by automation.
2. A Builder reviewing a process inherited from someone else. Taking over maintenance of a pipe with dozens of automations, the builder sorts by "Oldest Updated" to separate the stable, structural rules from the ones recently touched, focusing the review where it matters without relying on memory or outside documentation.
3. An Operations Manager confirming the date of a change. After a workflow adjustment early in the year, a question comes up about whether a given automation was changed before or after the year turned over. With the year visible in the "Last Updated" timestamp, the date is unambiguous and the confirmation is immediate, with no need to cross-check external records.
4. A Process Architect running periodic cleanup. During the quarterly review of a critical pipe, the architect sorts by "Last Updated" to see what changed since the last review, focuses the audit on the rules edited in that window, and keeps the process healthy without sweeping the entire set every time.
Most relevant for
- Pipe Admins
- Builders
- Process Architects
- Operations teams
