Spotify Connect to Facebook Sorry There Has Been a Temporary Error Please Try Again Later

Error Messages

Last Updated On May 2, 2022

You may encounter the following error messages while using the API Connector add-on for Google Sheets.

Error Messages

drive.google.com refused to connect
Error: Please enter asking name
ERROR: Please enter API URL path
ERROR: Destination canvass doesn't exist
Failed to run asking.
Failed to save request as the name already exists.
Limit Exceeded: URLFetch URL Length.
Request failed: Access not granted or expired.
Request failed: Aspect provided with invalid value: Header:HeaderKey
Asking failed: Bad request
Request failed: Information storage mistake
Request failed: DNS error
Request failed: Expected statement of type object, but instead had type boolean
Request failed: Expected argument of blazon object, just instead had type number
Request failed: Invalid argument
Request failed: Invalid POST body data
Request failed: Server response not in JSON, XML, or CSV format
Request failed: This action would increment the number of cells in the workbook above the limit of 10000000 cells.
Request failed: Your input contains more than than the maximum of 50000 characters in a single prison cell
Asking processed, no records plant
ScriptError: Authorization is required to perform that action
Service invoked too many times for one day: urlfetch
Nosotros received an mistake from xyz.com (###)
Other

IMPORTAPI Mistake MESSAGES

The following fault messages are specifically associated with the IMPORTAPI custom function. For information on these errors, please bank check the "Error Letters" section of this article instead.

Unknown function: 'ImportAPI'
Internal error executing the custom part
Pagination is simply available for paid users
Asking failed, cannot detect function split in object true
You do not have permission to telephone call setValues

ERROR MESSAGES

drive.google.com refused to connect

Like to the "ScriptError: Authorization is required to perform that activeness" error message, this error from Google occurs when logged in into multiple Google accounts at the same fourth dimension. Instead of seeing the regular add-on interface, y'all'll instead meet an image like this:

This is a known bug, so hopefully will be fixed by Google at some point. Until then, you can resolve this result by logging out from all other accounts before running the addition, or by opening in a new incognito window.

ERROR: Please enter request proper name

All API requests must accept a proper name earlier they can be run. This is true even if y'all don't save the request. Enter a proper noun (equally a all-time practice, choose a name that volition easily differentiate the request from other API requests in your sheet).

ERROR: Please enter API URL path

All API requests must contain an API URL. This URL should consist of at least a domain name and endpoint, e.g. www.apisite.com/v1/data. Optionally, it can as well contain query strings, due east.g. world wide web.apisite.com/v1/data?query=A&query=B.

Error: Destination sheet doesn't exist

Yous'll see this fault if you run your request without a destination sheet. To resolve, set up a destination sheet in your request earlier clicking Run.

Failed to run request

This mistake indicates that the request is unable to complete successfully, but didn't return any specific information about the cause of the problem. The primary cause of this fault is a asking that takes too long to complete and therefore hits Google's 6 min/request processing limits as described here.

To address, effort any or all of the post-obit:

reduce the size of your request. Well-nigh APIs provide some mechanism for limiting response size via query strings that filter for date or blazon.
change the report mode to "compact" or "grid", as these are normally faster than the default single row fashion.
if you are using pagination treatment, turn off the "fetch all" pick and add in a page count limit instead. When you lot select "fetch all", some APIs continuously ship back data such that your request times out. Adding a page count sets a stopping bespeak and so your request doesn't run forever.
use the visual field editor or a JMESPath expression to reduce the number of fields printed into your sail.

Failed to save asking as the name already exists.

All API requests must have a unique proper name. If you re-use a proper name that already exists, the request volition non salvage. To resolve, change the asking name and retry.

Limit Exceeded: URLFetch URL Length.

API Request URLs can not be longer than 2048 characters (info).

As a workaround you tin can use a URL shortener tool, due east.g. https://tinyurl.com/

Request failed: Access not granted or expired.

This error occurs when yous use the OAuth two.0 connectedness feature of API Connector. It ways your connection hasn't been activated, or access has expired. To resolve, navigate to the Connections screen and brand sure your OAuth 2.0 connection is agile. If you are not using a preset OAuth 2.0 connection, make sure you've selected Authentication = None.

Request failed: Attribute provided with invalid value: Header:HeaderKey

This means you've entered an invalid header key. Please check your API documentation and brand sure you've entered the header central exactly as written; e.one thousand. if the header key is 'api-key' make sure you oasis't entered 'apikey'. Also double-cheque that you haven't inadvertently pasted in an errant space or other character at the first or end of your header key.

Asking failed: Bad request

This means the API URL hostname is malformed. A asking like http://87000 would trigger this error. Brand sure you've entered a valid API URL, including a total hostname.

Asking failed: Information storage error

This is a temporary bug on Google'due south side related to the getProperty() method for saving triggers and requests. Bug reports take been filed and acknowledged.

If yous receive this error, delight wait and try your request once more after.

Asking failed: DNS mistake

This means the server you lot're trying to reach doesn't be or isn't responding. Check if your server has reported any outages. If not, double-check your API URL and run once again.

Request failed: Expected statement of type object, just instead had blazon boolean

This means that the server has responded with a boolean, i.e. 'truthful' or 'false', instead of a standard JSON object. API Connector but supports JSON, XML, and text/CSV responses (and receiving a true/false response to your asking unremarkably indicates some issue with the request itself).

Request failed: Expected argument of type object, but instead had type number

This means that your response output is a number when API Connector was expecting JSON. The most likely cause of this is a JMESPath query set to extract just a single number. To address, make certain your query returns a valid object, e.k. if you have a field named ID, add together a JMESPath query of {id:id} rather than merely id.

Request failed: Invalid argument

This occurs when your URL contains an invalid character, like a space or bracket. At that place are 2 common causes of this fault:

copying & pasting code snippets similar 'GET' into the API URL path box. This field can but have a valid URL.

not replacing case variables with actual values:

Wrong:              https://www.googleapis.com/youtube/v3/search?part=snippet&key={API_key}

Correct:              https://www.googleapis.com/youtube/v3/search?part=snippet&central=123456789

Request failed: Invalid Mail service body data

This error occurs when your Postal service body is incorrectly formatted. Ensure your POST torso is valid JSON. Consult this article for more than detailed instructions: Add together a Asking Body to a POST Request

Request failed: Server response non in JSON, XML, or CSV format

This mistake occurs when the server responds with data in an unsupported format, e.1000. an image or a boolean. 1 common cause of this fault is a request containing an invalid JMESPath expression.

Request failed: This action would increment the number of cells in the workbook above the limit of 10000000 cells.

Google Sheets permits a maximum of 10 million cells (documentation) per canvas, including empty cells. Therefore, you lot will see this error message from Google if your request would cause your canvas to surpass the limit. To address, try any or all of the post-obit:

Run your request in a fresh new sail
Split your requests into separate worksheets
Delete whatever unused tabs, rows, and columns from your worksheet
Limit the size of the data response you're requesting
Employ the field editor or JMESPath filters to print out fewer fields
Change the report style to compact or filigree.

Request failed: Your input contains more the maximum of 50000 characters in a single jail cell

This mistake occurs when the data response includes a field that contains more 50k characters. This occasionally occurs when pulling from APIs containing text fields with a lot of content.

Asking candy, no records found

This is more of a notification than an error message. Information technology means that there is no issue with the setup of your API request, simply the API service returned an empty response. If you were expecting information in the response, check the following:

brand sure you've entered the correct API URL
remove or edit query strings that could be filtering the results, such every bit dates and IDs
remove any JMESPath expressions equally they could be filtering out your results.

ScriptError: Say-so is required to perform that action

This is an error from Chrome that sometimes occurs when you have multiple Google accounts open in the aforementioned session. To resolve, sign out of your other accounts, or re-open up the add-on in a new incognito window.

Service invoked also many times for i day: urlfetch

This mistake message comes from Google itself. It is often, only not necessarily, associated with the IMPORTAPI custom function, every bit IMPORTAPI enables large volumes of API calls. Google has quotas on its usage, as described here: https://developers.google.com/apps-script/guides/services/quotas. A URL Fetch call is a request to get a URL, then one API request is one URL fetch call, and URL Fetch calls are limited to 20,000/day for consumer accounts.

Please note that Google applies this limit to each individual account (each email address), and sums together all the fetch calls from all the sheets you're using. This includes all scripts, functions, and other add-ons that y'all may exist running in improver to API Connector. Unfortunately Google doesn't provide any breakup of where URL fetch calls come up from, or any indicator of how close you are to the limit, and then you will need to review your sheets manually for excess URL fetch calls.

Pay special attending to functions like IMPORTJSON, GOOGLEFINANCE, and API Connector'southward IMPORTAPI equally these may produce URL fetch calls every infinitesimal. Please check this commodity for information on preventing backlog recalculation.

Nosotros received an error from xyz.com (###)

This fault message occurs when the API you're trying to connect to refuses to run your request and has returned an HTTP Response Condition mistake code.

Outset, click "evidence response" to see the verbal fault message returned by the server. This volition frequently warning you to the specific nature of the problem.

Since these errors come from the API, not from API Connector, you may need to bank check their API documentation to resolve the issue. You can besides await up the HTTP fault code displayed within the parentheses. This site contains brief explanations for all mistake codes: https://httpstatuses.com.

Other

In some cases, API platforms will accept a request but render an error message containing additional requirements or information equally their response. In those cases, their custom fault message will be displayed in the output canvas.

walterspoccour.blogspot.com

Source: https://mixedanalytics.com/knowledge-base/api-connector-error-messages/