How do I resolve report scheduling, export, and visualization issues in Amazon Quick?

Resolution

Resolve scheduled report failures

If the dataset refresh hasn't completed before the scheduled report triggers, then your scheduled reports fail or delay. To resolve this issue, take the following actions:

• Confirm that the dataset refresh completes before the scheduled report generation time. Then, adjust the report schedule to run after the dataset refresh completes.
• Confirm that you haven't removed the dashboard owner or co-owner from the account.
• Check that the recipients are part of your Amazon Quick subscription and that you shared the dashboard with the recipients. Amazon Quick has a maximum quota of 5,000 members for scheduled emails.
• Verify that you didn't pause the report schedule.
• Wait for current jobs to complete before you submit new ones. If you exceed the maximum quota of concurrent snapshot jobs, then you might receive the "LimitExceededException" error message. For each AWS account, you can run 12 snapshot jobs before you reach the maximum quota.

Resolve PDF export issues

If your PDF generation times out because of dashboard complexity, then your PDF generation fails or produces distorted output.

If you have sheets with a large number of visuals, complex calculated fields, or large datasets, then your datasets take longer to render and might time out. To resolve this issue, split complex dashboards into multiple sheets.

If the underlying SPICE dataset failed its last refresh, then the PDF export also fails. To resolve this issue, open the dataset to check the refresh history for the dataset.

If the PDF shows null values, gray boxes, or missing data that appears correctly on the dashboard, then there might be an issue with rendering timing. To resolve the issue, make sure that the visuals on the sheet have fully loaded before you generate the PDF. If you use direct query mode, then check that the data source is accessible and doesn't experience timeouts. For paginated reports, verify that the report layout is within supported page dimensions.

If you have complex custom visuals or visuals that rely on external images from private networks that can't be rendered in PDF exports, then the PDF formatting is distorted. To resolve this issue, simplify the visual formatting.

If only one dashboard fails while others succeed, then that dashboard's complexity or data source connectivity causes the failures. To resolve this issue, reduce the complexity for that dashboard.

Resolve CSV and Excel export issues

If you exceed export limits for CSV or Excel formats, then your CSV or Excel exports produce incomplete or incorrect data. To resolve this issue, take the following actions:

• Verify that you haven't exceeded export quotas.
• Verify that the visual contains data for those columns if certain columns appear empty in your exported CSV.
• Use CSV for larger datasets.

Resolve dashboard visualization showing missing or incorrect data

If your dashboard visuals don't display data or displays incorrect values, then check the dataset refresh status. Then, verify your filters and check your data source.

To check the dataset refresh status, complete the following steps:

1. Open Amazon Quick.
2. In the navigation pane, choose Data.
3. Select your dataset.
4. In the Refresh section, check the last successful refresh time.
   If you use SPICE, then make sure that the scheduled refresh successfully completed.
   If you use direct query mode, then verify the connectivity to the underlying data source.

To verify filters and parameters, take the following actions:

• Check whether your dashboard filters exclude the expected data.
• Verify that you correctly set the date range parameters.
• If the dashboard uses dynamic default parameters (DDP), then confirm they resolve correctly for the viewing user.

To check for data that disappeared after a specific date, take the following actions:

• Check if the data source schema changed.
• Confirm that you haven't changed the Row Level Security (RLS) rules to exclude the data.
• Check if you replaced the dataset or if the dataset replacement caused the report to fail.

Resolve snapshot job performance issues

If you have met the snapshot job throttling quota, then snapshot jobs are slow. To resolve this issue, run the StartDashboardSnapshotJob API operation.

To improve performance, take the following actions.

• Use SPICE datasets.
• Reduce the number of visuals per sheet.
• Simplify calculated fields.
• Stagger snapshot jobs.
• Use the DescribeDashboardSnapshotJob API operation to poll job status and implement retry logic with exponential backoff.