Custom Metrics error on saving

(1) Share

Report

Posted on by ldecuba1974

Hello,

one of my clients approached me with a question about custom metrics, telling me that they were trying out the custom metrics, tried a prompt and were satisfied with the results but were not able to save it, as they ran into an error when saving. Asked me if it's is because it's still in preview. I did not expect the preview status to be the issue so i tested it myself.

So i tried out a straight forward prompt, including a couple of categories, preview looked ok so i was about to move forward, saving the custom metrics but i ran into an error:
"Something went wrong and we couldn't create the metric"

I tried the exact same prompt, categories etc in my own tenant, it saved without any errors and i could see the new metric.

The most obvious difference i could see is that my environment is managed and on early release cycle and my client's environment is not managed.
Also there were no custom metrics saved yet, i am aware of the limit of 3 custom metrics, the agent sessions were even less in my own tenant (7 vs 20)
Roles on the environment were the same.

So my question is, as i could not find any documentation on the topic, is a managed environment a requirement for the custom metrics to be saved?

I could find any other difference at the moment, honestly i would expect the option being unavailable at all if that was the case..

Greetings,

Lisandro

custom metrics 2.png

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Bot analytics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 3,452 on at

Like
a
(0)

Report
Copy link

Link copied!
Based on the currently available documentation and known behavior, there is no indication that a Managed Environment is required to save custom metrics. The difference you're seeing is more likely due to a service issue, release-ring difference, tenant-specific configuration, or an undiscovered bug rather than the managed/non-managed status of the environment.

Given that:

the same prompt works in one tenant,

fails consistently in another,

and the error occurs only when saving,

this points more toward an environment-specific issue than an intentional product limitation. If others can reproduce the behavior in non-managed environments, it would strengthen the case for a product bug rather than a configuration requirement.

Was this reply helpful? Yes No
Suggested answer

Haque 3,686 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @ldecuba1974,

As alwasy preview features comes with many limitations and restrictions. We may see variations in terms of env. Type, release cycle and tenant configration. Apparantly, no official documentation states/suggests managed environment is a strict requirement, but practical experience shows some preview features behave differently or are limited in unmanaged environments.

First, I would suggest a testing in managed env. with similar setttings.

Sercond: please check the follwings:

Make sure tenant settings don't differ from yours.

Closely monitor copilot official release notes and preview features for updates on envrionment support.

If the issue is still there - let's go for suppor ticket.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No