Aww Snap Error on Chrome

[stubbstarbuck]

I get an Aww Snap error, usually once per day, on two reports that use data in multiple tables across multiple pages. I would like to use these as public screens.

I have tried reducing the size of the data set - now my Big Query query only pulls one day of data, which is usually less than 100 rows of information. Studio pulls the table result of these queries. Is there a better way to do this to avoid Aww Snap? Another screen without data has no issue, so it is definitely timing out calculating something during the refresh of the data. 

Any tips or suggestions?

[BetulA]

Hi, did you work out a solution to fix the issue?

[stubbstarbuck]

No, but I tried the following:

1) Reduce the size of the table down to a day from several years. This reduced the rows the BigQuery query had to crawl through from 100,000 to about 50.

2) Run a routine called from a Custom Query in Looker. 

3) Run the query directly in Looker as a custom query.

4) Run a view both ways.

5) Tried an Awww Snap Chrome plugin.

6) Changed refresh to be less frequent.

This also happens occasionally, though less frequently, with a report that has no data analysis and is just pulling images in from a Google bucket. Basically it appears that, if Looker can't get it's data within a second or so on a refresh, it just dies and never tries again.

I'm at the point of just hard coding this and giving up on Looker entirely.