Skip to main content
All CollectionsGoogle Looker Studio ConnectorTroubleshooting
What does this Looker Studio error mean and how can I fix it?
What does this Looker Studio error mean and how can I fix it?

Common errors in Looker Studio and how to avoid them

Viktor Tell avatar
Written by Viktor Tell
Updated over a week ago

In this article, we list the most common errors that our users report seeing when using our Looker Studio Connector. We will do our best to explain what they mean and our suggestions for how to avoid them.

Before you start applying the suggestions below make sure you try the basics; refresh data, refresh fields and reconnect the data source. Instructions for how to do this can be found in the article Google Looker Studio troubleshooting steps.

A few words on quota limits

Funnel and Google, (like any service provider with a lot of traffic) implements restrictions on how often a service can be used within certain time frames by the same entity. This is called quota limits. A user that is causing an unreasonable large load on a service risk degrading the performance for everyone else. Quota limits filter out traffic that is using the service beyond what is considered fair usage.

Google have a quota limit per Google user and day. This quota is shared between services like Looker Studio, Google Sheets and Google Calendar. You can read more about these limits in the Google Apps Script documentation.

Funnel uses a quota limit per Funnel Workspace, and it's shared across many of our features like the Data Explorer, the Looker Studio Connector and Data Warehouse Shares.

Most common errors in Looker Studio

1. "Service invoked too many times in a short time: exec qps"

What happened?

You've hit a Google quota limit with too many requests in a short time. From Google's documentation; "This indicates that the script called the given service too many times in a short period".

The error message can happen if the same Google user is doing heavy calculations either in Looker Studio (blends, custom fields, filters) and/or using Google Sheets with many custom functions as a data source in the Looker Studio Report.

โ€‹How do I avoid it?

  • Move transformation and filtering logic into Funnel (eg. custom fields)

  • Reduce complexity in the report (eg. number of charts per page, blends, custom fields)

  • If you have Google Sheets connected to the report, try and reduce the number and complexity

  • If you're using a shared Google account for many Looker Studio reports and Sheets, try to split it up by connecting to Funnel with a different Google user

2. "Service invoked too many times for one day: urlfetch"

What happened?

You hit your daily Google quota limit. From Google's documentation: "This indicates that the script exceeded the total allowable execution time for one day. It most commonly occurs for scripts that run on a trigger, which have a lower daily limit than scripts executed manually". Specifically, it means that the Google user have had more than 20 000 data requests per day across the different Google Services.

How do I avoid it?

  • Reduce the complexity and amount of Google Services your Google user is using

  • Use a different Google user for the Looker Studio report

  • User a different Google users for the data sources in the Looker Studio report

3. "Distributed query rate limit per minute exceeded"

What happened?

You hit a Funnel Workspace quota limit. The amount of work required to satisfy all the queries that are being made from a single Workspace in a 60-second period is higher than our limit, and some of the requests are being throttled.

How do I avoid it?

  • Wait a minute and try again, the rate limit is within a 60-second period.

  • Use a Data Share which includes the fields you want to use.

  • Reduce the number of widgets per page. (split the page into several pages)

  • Reduce the number of fields per chart.

  • Reduce the volume of queries by adding filters on data sources in your Data Share.

  • In the article Why is my Google Looker Studio report so slow you will find more suggestions on what steps to take to reduce the amount of work required by the report.

4. "Too many rows, try using a shorter date range or fewer dimensions"

What happened?

You hit a Funnel quota limit. The query would result in too many rows and was therefore aborted, this is done for performance reasons, and to avoid sending huge or incomplete responses.

How do I avoid it?

  • In the article Why is my Google Looker Studio report so slow you will find suggestions on what steps to take to reduce the amount of work required by the report, for instance

    • Reduce the complexity of your report (eg. number of charts per page, number of fields per chart)

    • Reduce the volume of data that Looker Studio needs to handle by applying filters to your Looker Studio Data Share

  • Make sure you're within the limits of Funnel's fair usage

5. "Missing or invalid date range"

What happened?

We believe this to be a Looker Studio bug and have reported this in Google's issue tracker.

How do I avoid it?

Some users have reported success by trying the following:

  • Change the date range in Looker Studio

  • Refresh fields

  • Reconnect your data source

  • Replace your data source

6. "System Error"

What happened?

This error message points to an error within Google Looker Studio. The request never reached Funnel so we don't know any more details than what is shown here.

How do I avoid it?

Some users have reported success by tinkering with the following:

Seeing other errors?

Please reach out via the in-app support chat or send an email to For us to give you the best possible help we refer you to the article How to report a problem. We'll do our best to help and will update this article with new common errors and how to avoid them as we learn more.

Did this answer your question?