How do I configure and troubleshoot SPICE dataset refresh in Amazon Quick?

Resolution

Configure SPICE dataset refresh schedules

You can create up to five refresh schedules per dataset. To create a refresh schedule, see Refreshing a dataset on a schedule.

Configure incremental refresh schedules

For SQL-based data sources, configure an incremental refresh to query data only within a specified look-back window.

Manually refresh a SPICE dataset

To perform an on-demand refresh, see Refreshing a dataset.

Troubleshoot dataset refresh issues

Refresh timeout errors

If you query the data source and the dataset includes large data volumes, then you might get a refresh timeout error message.

To resolve timeout errors, limit the data that you import, and then use incremental refresh to reduce the amount of data that processes.

For more information, see How do I resolve query timeout errors in Quick Suite?

Dashboard out of date after refresh

If your dashboard doesn't display updated data after a dataset refresh, then take the following actions:

• Check the Refresh tab on the dataset details page to verify the dataset refresh completed successfully.
• For SPICE datasets, confirm that you configured the refresh schedule to be active and running at the expected time.
• For direct query datasets, refresh the dashboard page in your browser or select a different sheet to reload the visual.
• Check that the dashboard uses the expected dataset.

Refresh permissions errors

If you didn't configure the permissions for your AWS Identity and Access Management (IAM) role or user that's associated with the data source, then your dataset refresh might fail. The dataset refresh might also fail if you don't have the AWS Key Management Service (AWS KMS) key or AWS Lake Formation permissions..

To resolve permission-related refresh failures, verify that the data source credentials are current and valid. Then, update expired database credentials or OAuth tokens in the data source settings. For data sources that use AWS Secrets Manager, verify that the secret contains valid credentials and that Amazon Quick has access to the secret.

Then, check that you configured the correct permissions for the IAM service role for Amazon Quick to access the data source. For Enterprise edition, verify that the default access policy allows access to AWS resources. Also, make sure that the relevant IAM policy assignments are turned on for the user or group that owns the dataset. If the data source uses a run-as role, verify that you attached the correct permissions to the IAM role to access the data source. The trust relationship must also allow Amazon Quick to assume the role.

To make sure that the Amazon Quick user or role has the required table-level permissions, complete the following steps:

1. Open the Lake Formation console.
2. Choose Data permissions.
3. Filter by the target database and table to confirm that the Amazon Quick user Amazon Resource Name (ARN) has the Select permission.
   Note: For more information, see Viewing database and table permissions in Lake Formation.

Parallel refresh failures

If multiple datasets simultaneously refresh, then some datasets might fail because of constraints at the data-source level.

To resolve parallel refresh failures, stagger refresh schedules so that datasets don't refresh at the same time. Then, use incremental refresh to reduce the load per refresh operation.

Related information

Refreshing visuals in Quick Sight

Refreshing SPICE data

Automate SPICE dataset refreshes using Amazon Quick APIs

How do I resolve query timeout errors in Quick Suite?