I need to force a SPICE refresh to fail (to test downstream processes)

[ssquicksight]

I have alerts set up through PagerDuty to notify of failed dataset refreshes. I need to test the setup, and am seeking a way to force a SPICE dataset to fail a refresh. Preferably the dataset would not be required to be large in order to minimize SPICE usage.

Any ideas on how to accomplish this?

[Brett]

Hi @ssquicksight and welcome to the QuickSight community!
I’ve included some documentation below that explores ways a SPICE refresh could fail, as well as error codes you may encounter.
I would suggest using this information to test for failure.

In terms of a way to check with a smaller dataset; there’s an error code ‘number_parse_failure’, which occurs if you have a value in a numeric field that’s not a number. You could try adjusting a value in a numeric field early in your dataset.

Quicksight SPICE dataset not refreshing the data

I have a dataset which contains up to 98 M rows and is scheduled to refresh every hour, it was refreshing fine until 2nd Aug’24, however, from 2nd Aug’24 it has failed to refresh and the data is not loading to Quicksight. I’m not sure why this is happening. Though it shows refresh completed after taking 5, or 6 hrs the data is not reflected in the dataset or analysts. I’m just wondering why this is happening. [image]

SPICE ingestion error codes - Amazon QuickSight