Insights & updates from our experts
Last week’s release introduced the ability for a provider to stop the SLA clocks under certain conditions, using automation rules. This temporarily removes the accountability of a provider, for example when a workflow has to wait for an approval of the customer. This functionality can now also be enabled from the task templates.
A checkbox ‘Provider not accountable’ has been added to task templates, which – when enabled – stops the SLA clocks of the requests that are linked to the workflow of this task. The checkbox is available to workflow managers, account administrators and designers.

In the ‘Task’ view, it is indicated for which tasks the provider is made not accountable for SLA breaches.


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)











