Insights & updates from our experts
A new category for workflow tasks has been added to tasks and task templates. In addition to Risk & Impact, Approval, and Implementation tasks (and the Fulfillment Placeholder task, which was added for the Xurrent Shop), tasks can now also be of the category ‘Automation’.
When a workflow task is completely handled by automation, either through automation rules or using external automation, it makes sense to be able to treat it differently from other tasks. There is no need to be able to assign it to a team or specialist, there is no need for notifications, and there is no need for many of the fields that are available for regular tasks. This makes the Task form for automation tasks very simple.

A good candidate for an Automation task would be a task that consists of only automation rules, such as a task that prepares a workflow and then completes itself. Automation tasks can easily be recognized in the Gantt chart by the automation icon.

Automation tasks are not visible in the Inbox and can only be updated by OAuth applications, the workflow manager or a person with the Account Administrator role.

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)














