- Newest
- Most votes
- Most comments
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:
-
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.
-
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.
-
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:
-
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.
-
Manually refresh the dataset: Try forcing a manual refresh of the SPICE dataset.
-
Check for resource constraints: Verify that there are no resource limitations affecting your QuickSight account.
-
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
Relevant content
asked 7 years ago
asked 3 years ago
- AWS OFFICIALUpdated a year ago
