Insights & updates from our experts
Since the end of last year, it is possible in Xurrent to make a recurrent reservation for a configuration item. It is now also possible to discern with an automation rule whether a reservation is one-time only, or recurring. For this, the Boolean field Recurrent has been exposed to the automation rules.

This can be helpful for organizations that want to take automated action on reservation requests that are not recurrent. For example, for adding the reservation date to the request subject, which would not make sense on recurrent reservations.

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.

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.















.webp)
.webp)

.webp)












