# Dashboard opens with data but filters show error "Request took too long. try again later" **URL:** \ **Category:** Q&A\ **Tags:** error, developer, quick-sight\ **Created:** [October 18, 2023, 9:00am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131 "2023-10-18T09:00:38Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Ali\_B](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@Ali\_B](https://community.amazonquick.com/u/Ali_B)\ **Post date:** [October 18, 2023, 9:00am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/1 "2023-10-18T09:00:38Z")
This error happens when I open the dashboard. it works fine from the analysis. Dashboard: ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/d/da0aefd3280e7ba788fe07f99093dc883d835017.png) Analysis: ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/c/c1bc5d2037909f059fbeeabcde491c56334bfbfa.png) ---
**Author:** ![ErikG](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/erikg/32/14524_2.png) [@ErikG](https://community.amazonquick.com/u/ErikG)\ **Post date:** [October 18, 2023, 9:18am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/2 "2023-10-18T09:18:50Z")
Hi @Ali_B , what is the exclamation mark telling? BG ---
**Author:** ![Ali\_B](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@Ali\_B](https://community.amazonquick.com/u/Ali_B)\ **Post date:** [October 18, 2023, 9:24am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/3 "2023-10-18T09:24:59Z")
![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/f/f1095554a0bf166f0316f0e8ef918723fce4419c.png) ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/9/9d5bed69546454a6874c98ec34f2966dbd5958d0.png) The data in the main table loads fine. it just the filtes. ---
**Author:** ![ErikG](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/erikg/32/14524_2.png) [@ErikG](https://community.amazonquick.com/u/ErikG)\ **Post date:** [October 18, 2023, 9:28am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/4 "2023-10-18T09:28:10Z")
can you try to publish with a specific element instead of “all” on the filter? ---
**Author:** ![Ali\_B](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@Ali\_B](https://community.amazonquick.com/u/Ali_B)\ **Post date:** [October 18, 2023, 9:33am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/5 "2023-10-18T09:33:09Z")
it works for a while, then users start seeing the same errors. When I first published the dashboard, it worked fine even without preselected values. then after a day or so it started showing errors ---
**Author:** ![ErikG](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/erikg/32/14524_2.png) [@ErikG](https://community.amazonquick.com/u/ErikG)\ **Post date:** [October 18, 2023, 9:35am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/6 "2023-10-18T09:35:21Z")
Is you dataset growing or was changed in the meantime? ---
**Author:** ![Ali\_B](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@Ali\_B](https://community.amazonquick.com/u/Ali_B)\ **Post date:** [October 18, 2023, 9:38am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/7 "2023-10-18T09:38:14Z")
The dataset is definitely growing, it is also being worked on although those filter fields are the same. ---
**Author:** ![ErikG](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/erikg/32/14524_2.png) [@ErikG](https://community.amazonquick.com/u/ErikG)\ **Post date:** [October 18, 2023, 9:55am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/8 "2023-10-18T09:55:08Z")
Because it seems there are to many data or the query is not performing well. ---
**Author:** ![Ali\_B](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@Ali\_B](https://community.amazonquick.com/u/Ali_B)\ **Post date:** [October 18, 2023, 10:08am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/9 "2023-10-18T10:08:10Z")
The dataset is on SPICE though. I’m not sure what the “query performance” means when your data is loaded in memory on SPICE ---
**Author:** ![ErikG](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/erikg/32/14524_2.png) [@ErikG](https://community.amazonquick.com/u/ErikG)\ **Post date:** [October 18, 2023, 10:20am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/10 "2023-10-18T10:20:04Z")
Ok. In case of SPICE its not relevant. Are the filter cascading or standalone? I would try to check if i can downsize the elements in a filter and see if it will work. ---
**Author:** ![Ali\_B](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@Ali\_B](https://community.amazonquick.com/u/Ali_B)\ **Post date:** [October 18, 2023, 10:22am UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/11 "2023-10-18T10:22:34Z")
@ErikG By cascading do you mean the “only show relevant values” option on filters? then they are standalone. ---
**Author:** ![bergqdou](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/bergqdou/32/4265_2.png) [@bergqdou](https://community.amazonquick.com/u/bergqdou)\ **Post date:** [October 24, 2023, 10:49pm UTC](https://community.amazonquick.com/t/dashboard-opens-with-data-but-filters-show-error-request-took-too-long-try-again-later/20131/12 "2023-10-24T22:49:07Z")
Hi @Ali_B Some things to check: 1. How many distinct values are in the fields? Is it a large number that’s causing the performance issue? Also how many rows are in the SPICE dataset. I believe there are a few options to solve this. 1. As @ErikG mentioned ‘only show relevant values’ will cut down the number of values returned in the filter list. 2. Change the control to ‘Dropdown - multiselect’ so it’s not preloading every value in the dropdown. 3. Create a dataset specifically for the filters/controls that only contains a unique list of values. Outlined here: [Improve Filter performance for Direct Query Dashboards: 2023 Amazon QuickSight Learning Series](https://community.amazonquick.com/t/improve-filter-performance-for-direct-query-dashboards-2023-amazon-quicksight-learning-series/14391)