Hi ,
I’m encountering a puzzling issue in Amazon Quick Sight and would appreciate any insights.
Recently, a customer raised a concern that the data in a Quick Sight dashboard was not refreshing.
I verified the following:
• The base tables and derived tables in the source (Redshift) were up to date.
• All ETL jobs ran successfully with no errors.
• The SPICE dataset refresh and Quick Sight reporting cadence were functioning as expected.
Despite everything appearing normal, the data in the Quick Sight visuals was not reflecting any new or modified rows. No recent updates were visible, even though the source had fresh data.
As a temporary fix, I dropped and recreated the underlying table in quicksight with the same schema and reloaded the data. After doing this, the updated records started to reflect correctly in Quick Sight.
I’m trying to understand:
• Why this could have happened?
• Is this a caching issue with SPICE or a known issue with schema recognition?
• Are there best practices to avoid such problems in the future?
Hi @sujanaab
Configure incremental refresh your dataset to pull only new or updated rows based on a reliable date field.
Monitor SPICE Capacity: In the Quick Sight console under Manage SPICE, maintain at least 10–20 % free capacity.
Data Source Availability: The data source may be experiencing issues, leading to long refresh times. Verify the availability and performance of the data source. Ensure that the data source is accessible and that there are no network issues or timeouts during the refresh process.
Changes in Data Schema : If there were any changes in the table/view schema in the data source by removing or adding fields, it might be causing issues with the refresh process. Review any changes in the data source or dataset configuration around that time.
Hi @sujanaab
It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.
If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.
Thank you!
Hi @sujanaab
Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.
Thank you!