Anomaly Detection - Why it keeps reseting after configuration and run

Hello, everyone!

I’m using anomaly detection on a redshift connection.
I am able to configure it (and can actually see a chart in the “Set Anomaly Detection” page).

But when I click in the “Run Now” button, it runs for a while and then the “Run Now” button appears again. The actual analysis is never shown.

Is it a issue with the data source?


Hmm it seems to be working on my account with Athena. Don’t know if it would be caused by a data source issue. I’ll flag this as an error to see if someone else knows about it.

Maybe a couple of things to check,

  1. Do you have the dataset as Direct Query or SPICE? I would suggest SPICE
  2. How much data are you scanning? Can you limit the dataset and see if that works?

Thank you Max.

  1. I’m using SPICE
  2. Its a small dataset (7mb)

And another information, my data is weekly. In my date dimension I only have the last days of the week (Saturdays). This may affect something?

That might be affecting it.

For anomaly detection to work it needs enough data to scan.

Here are the requirements.

Hi, @mvilela. Did the response from @Max answer your question? 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 Q&A Forum!