Hi everyone,
I’m using anomaly detection on a dataset sourced from Redshift. While I can configure it successfully, clicking “Run Now” doesn’t initiate the analysis. The button simply reappears after a while.
I’ve already reviewed a similar issue in the Amazon QuickSight Community (Anomaly Detection - Why it keeps reseting after configuration and run - Question & Answer - Amazon QuickSight Community), but the provided solution hasn’t resolved my problem.
Any insights or suggestions to troubleshoot this issue would be greatly appreciated!
Thank You
@Abobbala ,
When I click “Run Now” in the analysis , the anomaly detection runs on the data [ in the screenshot 3 dots ]
Once complete , click “Explore Anomalies” provides more information
Maybe publish the dashboard with anomaly schedule configured ( Adding an ML insight to detect outliers and key drivers - Amazon QuickSight ) and check if it shows any results ?
If not , I would recommend to open a support case. Here are the steps to open a support case so that we can help you further: Creating support cases and case management - AWS Support . If your company has an internal IT team, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team. They’ll open an AWS Support case on your behalf.
Kind regards,
Koushik
Did this solution work for you? I am marking this reply as, “Solution,” but let us know if this is not resolved. Thanks for posting your questions on the QuickSight Community!
@Koushik_Muthanna,
Thank you for the response.
I followed the document on adding an ML insight to detect outliers and key drivers in Amazon QuickSight Adding an ML insight to detect outliers and key drivers - Amazon QuickSight. However, I’m still encountering an issue. After configuring and saving the anomaly detection, when I run it, the “Run Now” option reappears after some processing time.
Thank you for letting us know. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!
