Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
Two small but helpful improvements have been released to help administrators who are in charge of the webhooks that their organization has set up in Xurrent. The first improvement ensures that the value in the URI field of a webhook (excluding any user credentials or parameters) is included in the email messages that Xurrent sends out when a webhook runs into an exception.
The second improvement ensures that an email gets sent out when a webhook, which had failed earlier, has started to function normally again after one or more retries. This will prevent an administrator from trying to resolve a webhook issue after it has already recovered.
Note that these email messages are sent to the email address specified in the field ‘Mail exceptions to‘ of the webhook.
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