Skip to content

Problem with SPICE in Quicksight - No data imported

0

Good morning. I'm having trouble importing data into a dashboard in QuickSight.

My process works like this: the data is saved in Athena, an engine is run to modify the data, it's saved back to Athena, and a dataset is created from those tables.

It worked perfectly for over a month (no changes were made, and it's updated daily). But today, QuickSight is telling me that 0 rows were imported from Spice.

However, if I check the dataset, the refresh tab shows that 3400 rows were imported (which is normal; it's usually 3100-3500). But the summary tab shows "no rows imported." The thing is, sometimes it says yes, and then after 5 seconds it reverts to saying no rows were imported.

I've tried duplicating it, or editing a calculated field, and when I try to save or duplicate it, I get an error message. It's strange because I own the dataset.

If anyone knows how I can fix this, I'd appreciate it, as the AI ​​suggests I have to recreate it (which I really don't want to do).

asked 9 months ago285 views

1 Answer
-2

Based on your description, you're experiencing an issue with QuickSight SPICE where the dataset appears to have imported data (3400 rows) in the refresh tab, but the summary tab shows "no rows imported" and the dashboard isn't displaying any data.

This sounds like it could be one of several issues:

  1. Permission or policy configuration issue: You might be encountering a "NO_SCOPEDOWN_POLICY_CONFIGURED" error. Even though you own the dataset, QuickSight's internal scopedown policy logic for datasets might be causing access problems after recent security changes or updates.

  2. Connection issue between QuickSight and Athena: There might be a communication problem during the SPICE ingestion process, similar to the "Invalid protocol sequence" errors that can occur with database connections.

  3. Dataset corruption: The dataset metadata might have become corrupted, causing inconsistent behavior where it shows data was imported but then reverts to showing no data.

Here are some troubleshooting steps you can try:

  1. Check QuickSight permissions: Go to QuickSight Admin → Security & Permissions, find your user, and verify all permissions are correct. You might need to create and assign a scopedown policy (even a permissive one) temporarily to reset internal references.

  2. Manually refresh the dataset: Try forcing a manual refresh of the SPICE dataset.

  3. Check for resource constraints: Verify that there are no resource limitations affecting your QuickSight account.

  4. Export and reimport using Asset Bundle: As a last resort, you can use the QuickSight Asset Bundle feature to export your dashboard and dataset configuration, then reimport it with a new prefix. This effectively recreates the dataset without manually rebuilding everything.

If the issue persists, you might need to contact AWS Support, as this could be related to internal QuickSight service issues that require their intervention.
Sources
QuickSight Error: NO_SCOPEDOWN_POLICY_CONFIGURED – Unable to Refresh Manually, Duplicate, or Edit Dataset | AWS re:Post
Quicksight ERROR: Invalid protocol sequence 'P' while in PortalSuspended state. | AWS re:Post

answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.