Quick Sight Datasets Stuck Trying To Refresh

When QuickSight datasets get stuck in a refresh state after an outage, this can be frustrating, especially when cancel-ingestion commands don't seem to work despite returning a 202 status code.

Based on your situation, here are some approaches to resolve the issue:

1. For the datasets showing the NO_SCOPEDOWN_POLICY_CONFIGURED error, this typically occurs after user security changes. This error prevents refreshing, editing, or duplicating datasets even when the user is an Admin and owns both the dataset and data source.

2. Since the cancel-ingestion commands aren't working, you might need to try the asset bundle export/import approach:

• Export the affected datasets using the start-asset-bundle-export-job command
• Reimport them using start-asset-bundle-import-job with appropriate parameters
• This effectively recreates the dataset without the corrupted references

3. Another approach is to check the security and permissions:

• Go to QuickSight Admin → Security & Permissions
• Find the IAM or IAM Identity Center user
• Create and assign a scopedown policy (even a permissive one)
• Try to refresh the dataset
• If successful, you can remove the scopedown policy afterward

4. You could also try reassigning dataset permissions using the update-data-set-permissions AWS CLI command, which might reset the internal references.

Unfortunately, there's no specific timeframe for when stuck datasets might clear on their own after an outage. The approaches above are more reliable than waiting for an automatic resolution.
Sources
QuickSight Error: NO_SCOPEDOWN_POLICY_CONFIGURED – Unable to Refresh Manually, Duplicate, or Edit Dataset | AWS re:Post
CancelIngestion - Amazon Quick Sight
Quick Sight API Operations to Control Data Resources - Amazon Quick Sight