Please contact the Quick team to resolve this issue

Q&A
, ,
1

I had worked on an analysis an dashboard this previous Friday and it worked perfectly. I opened the same report today and I find the error attached in the picture. I have uploaded another dataset to test it is not spice or an error for a calculated field and the upload works fine, the error is inside an analysis/dashboard. I have also changed regions to see if it has anything to do with that and still, same error.

Captura de pantalla 2025-12-22 a la(s) 10.48.12 a.m.
Captura de pantalla 2025-12-22 a la(s) 10.48.12 a.m.906×720 24.3 KB

Thanks in advance.

2

Hi @Isabel_Navarro1 ,

I personally have never come across this error before so I think your next best steps would be to submit a support ticket. I would refer to this resource on how to submit one (Case management - AWS Support).

Please let us know if anything is uncovered after the support team investigates your issue!

3

I’m experiencing a persistent issue with several dashboards in the us-east-2 region. All visuals show the generic error message: “Please contact the Quick team to solve this issue.”

I have already performed extensive troubleshooting to rule out configuration issues:

  1. Direct Query works: If I switch the datasets to Direct Query, the visuals render correctly. The issue only happens when using SPICE.

  2. SPICE Capacity: I have confirmed that we have plenty of available SPICE capacity in the account.

  3. Tested multiple Data Sources: The error persists regardless of the source. I’ve tried Athena, Aurora, and even local CSV files; all fail when imported into SPICE but work fine in Direct Query.

  4. Recreating Resources: I’ve created new datasets and new Analysis from scratch, but the error persists in the new resources as well.

This seems to be an internal issue with the SPICE engine in our region rather than a dataset configuration problem.

Attached are the error details from one of the affected visuals:

  • Region: us-east-2

  • RequestId: 02bfb39a-200b-4d71-8124-4b58a3ff4ad9

  • Timestamp: 1766432246380

Is anyone else experiencing this in us-east-2? Could a member of the QuickSight team please look into this RequestId?

image
image1035×388 83.1 KB

4

Thank you, the issue has been resolved

5

Hi @david.riveros,

If you are still experiencing this issue, I would also recommend to submit a support ticket. I would refer to this resource on how to submit one (Case management - AWS Support).

If you have any additional questions, please create a new post in the community as this post has been solved. This will help so that your additional questions will be more visible to our Quick Experts!