"No anomalies found" where anomaly detection disabled | Community
Skip to main content
ercankantar
Level 2
September 28, 2018
Solved

"No anomalies found" where anomaly detection disabled

  • September 28, 2018
  • 6 replies
  • 7638 views

Why do I see "Searching for anomalies" and "No anomalies found" texts, although I disabled anomaly detection both in the chart settings and also in all metrics of the basis table?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by RameshAnalytics

Here you go to report the bug to customer care: customercare@adobe.com

More info on the support is at Analytics Cloud Help | Adobe Analytics Cloud Learn & Support

Thanks,

Ramesh

6 replies

Gigazelle
Adobe Employee
Adobe Employee
October 18, 2018

Hi Ercan, that looks like a bug. If you reach out to Customer Care, we can get it to engineering for a fix.

ercankantar
Level 2
October 19, 2018

Hi Gigazelle​, thanks! It it's a bug, why am I supposed to reach out to Customer Care? It should just be fixed.

Gigazelle
Adobe Employee
Adobe Employee
October 19, 2018

Our current workflow for reporting bugs is via Customer Care, as that is the channel that allows us to get individual company/user details. It also provides you with a channel to get updates on the status of the bug.

I'd be happy to report the bug on your behalf, but before doing so I'd need to know exactly how the report was created so I can see the 'no anomalies' despite it being turned off. That would be the exact same information as what Customer Care would need though, so going through an already-established process would provide better results in the long run.

ercankantar
Level 2
October 19, 2018

OK, can you provide details on how I can report the bug to Customer Care?

RameshAnalyticsAccepted solution
Level 4
October 20, 2018

Here you go to report the bug to customer care: customercare@adobe.com

More info on the support is at Analytics Cloud Help | Adobe Analytics Cloud Learn & Support

Thanks,

Ramesh

Level 5
June 21, 2019

Gigazelle

It's been 8 months since OP noted this bug, and it still hasn't been fixed. Is the development backlog causing the delay, or is it because not enough users have reported the issue?