Blog
Insights & updates from our experts
.webp)
.webp)
To make sure that people do not accidentally select an inactive configuration item (CI) where it does not make sense to link an inactive CI, Xurrent no longer offers inactive CIs when someone is relating a CI to a:
- Request Template
- Task Template
- Service Instance
- Contract
- Reservation Offering
- Person
- Short URL
An inactive CI is a configuration item which status is ‘Archived’, ‘To Be Removed’, ‘Lost or Stolen’ or ‘Removed’.
It is still possible to link any CI, with the exception of the ones that have already reached the status ‘Removed’, to requests, problems and implementation tasks. The reason for this is that, even though the status of a CI may be ‘Archived’, ‘To Be Removed’ or ‘Lost or Stolen’, eventually an action will still be needed to remove it. To get someone to take this action, an assignment will need to be registered and this assignment will then need to be linked to the CI that is to be removed.
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