Error with refresh data

Question & Answer
1

That error is appearing to me, but I’m not cancelling the refresh

Amazon Invalid operation: Query (331946709) cancelled on user’s request;

image
image709×248 16.9 KB

1 Like
2

Hi @Francisco : Can you please verify the SQL that you are trying to refresh . Take the sql and run in the database to ensure there is NO syntax issue . Then you can refresh it from QuickSight. Also it is a customized data set or a simple data set and you want to refresh and store the data in Spice. Please give more details so that it will help us in giving right solution.

Regards - San

1 Like
3

Hey Sanjeeb,

I tested the querie and it’s not giving me any error at hubble. It’s a simple dataset.

I tested the dataset with other queries and it worked. But the query that I want, is only working at hubble.

Which detail I can give you more? So I can go for it, thanks for the attention!

Regards,
Francisco

4

Hey Sanjeeb,

I tried again at hubble, and it didn’t worked again.

Game this error - I’m diving deep on it

Message:ERROR: Query (332719327) cancelled on user’s request Detail:

5

Thanks @Francisco - What is the total volume of the data, can you please see the execution time out of quicksight like ( re write the sql using CTE and take the count) so that it will give how much time to get the result. QuickSight has a timeout of 2 Mins ( I believe) and if the sql is taking more than it will fail. However if the data set is SPICE mode, the timeout parameter is 30 Mins.

To investigate the issue, also requesting you please raise a ticket to AWS ( see the link how raise a request - Creating support cases and case management - AWS Support). This will help AWS team to connect and share your screen so that they can validate the issue. If you do not have access to raise a ticket, request you AWS admin, they can help you on this.

Looking at your information, I am thinking it is not problem with QuickSight rather with sql complexity or performance issue with SQL. Also can you create a new data set with same sql and try once.

Hope the above details will help you.

Regards - San

6

Thanks Sanjeeb, I’m going to use your info to look forward into a solution.

1 Like