Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
The ‘Aging’ reports present how long records in Xurrent have been in a certain status or condition. The ‘Open Requests Aging since Registered’ report, for example, shows the number of not completed requests, grouped in time intervals during which they were created. Until now, these intervals were fixed. Their time spans were chosen to reasonably distribute the records over these intervals, even though other intervals might make more sense to some organizations. Other organizations might even prefer more, or less intervals. All that is now possible.
Account administrators can now update the intervals of ‘Aging’ reports by clicking the Edit Report button (the button with the pencil) and then selecting the current intervals.
The intervals can be set from minutes to years, where each next time span starts after the previous one. More intervals can be added by clicking ‘Add Interval…’.
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
Service Management
News
Enterprise
How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.
8 Mins
May 30, 2026
Service Management
Enterprise
Integrations