Server Error Occurred Please Try Saving the Project Again Google Sheets Script

Mistake 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 request name
ERROR: Please enter API URL path
ERROR: Destination canvas doesn't exist
Failed to run request.
Failed to save asking 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
Request failed: Bad request
Request failed: Data storage fault
Request failed: DNS error
Request failed: Expected argument of type object, simply instead had type boolean
Request failed: Expected statement of blazon object, but instead had type number
Request failed: Invalid argument
Request failed: Invalid Mail trunk data
Request failed: Server response not in JSON, XML, or CSV format
Request failed: This activeness would increment the number of cells in the workbook to a higher place the limit of 10000000 cells.
Request failed: Your input contains more than the maximum of 50000 characters in a single jail cell
Asking processed, no records found
ScriptError: Authorization is required to perform that action
Service invoked too many times for 1 day: urlfetch
We received an error from xyz.com (###)
Other

IMPORTAPI Error Letters

The following mistake letters are specifically associated with the IMPORTAPI custom part. For data on these errors, please check the "Error Letters" department of this article instead.

Unknown function: 'ImportAPI'
Internal error executing the custom part
Pagination is only available for paid users
Request failed, cannot observe function split in object true
Y'all do non have permission to call setValues

ERROR Messages

drive.google.com refused to connect

Similar to the "ScriptError: Authorization is required to perform that action" mistake message, this error from Google occurs when logged in into multiple Google accounts at the aforementioned time. Instead of seeing the regular add together-on interface, you'll instead see an image like this:

This is a known problems, so hopefully volition exist fixed by Google at some signal. Until and then, you can resolve this issue by logging out from all other accounts before running the add-on, or past opening in a new incognito window.

ERROR: Please enter request name

All API requests must have a name before they can exist run. This is truthful fifty-fifty if y'all don't save the asking. Enter a name (every bit a best practise, cull a name that volition easily differentiate the request from other API requests in your sheet).

Mistake: Delight enter API URL path

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

Mistake: Destination sheet doesn't exist

You'll see this error if you run your request without a destination sheet. To resolve, set a destination canvass in your asking before clicking Run.

Failed to run request

This mistake indicates that the request is unable to complete successfully, but didn't return any specific information nigh the crusade of the problem. The primary cause of this error is a request that takes also long to complete and therefore hits Google'due south six min/request processing limits as described here.

To address, endeavor any or all of the following:

reduce the size of your request. Most APIs provide some mechanism for limiting response size via query strings that filter for date or type.
change the report manner to "compact" or "grid", as these are unremarkably faster than the default single row fashion.
if you are using pagination handling, turn off the "fetch all" option and add in a folio count limit instead. When you select "fetch all", some APIs continuously send back data such that your request times out. Adding a page count sets a stopping indicate 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 sheet.

Failed to salve request as the proper noun already exists.

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

Limit Exceeded: URLFetch URL Length.

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

Equally a workaround you tin can apply a URL shortener tool, e.1000. https://tinyurl.com/

Request failed: Access not granted or expired.

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

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

This means you've entered an invalid header key. Delight check your API documentation and make sure you've entered the header fundamental exactly every bit written; e.g. if the header key is 'api-cardinal' make sure y'all haven't entered 'apikey'. Also double-check that you haven't inadvertently pasted in an errant space or other graphic symbol at the beginning or terminate of your header central.

Request failed: Bad request

This means the API URL hostname is malformed. A request like http://87000 would trigger this error. Make certain you've entered a valid API URL, including a full hostname.

Request failed: Data storage mistake

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

If you receive this error, delight await and try your request over again afterward.

Request failed: DNS mistake

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

Request failed: Expected argument of type object, simply instead had type boolean

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

Request failed: Expected statement of type object, simply instead had blazon 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 excerpt merely a unmarried number. To address, make sure your query returns a valid object, e.g. if y'all accept a field named ID, add a JMESPath query of {id:id} rather than only id.

Request failed: Invalid argument

This occurs when your URL contains an invalid character, like a space or bracket. There are ii common causes of this error:

copying & pasting code snippets like 'Become' into the API URL path box. This field can just accept a valid URL.

not replacing example variables with actual values:

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

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

Asking failed: Invalid POST body data

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

Asking failed: Server response not in JSON, XML, or CSV format

This error occurs when the server responds with data in an unsupported format, due east.thou. an image or a boolean. One common cause of this error is a request containing an invalid JMESPath expression.

Asking failed: This activity would increment the number of cells in the workbook to a higher place the limit of 10000000 cells.

Google Sheets permits a maximum of 10 1000000 cells (documentation) per sail, including empty cells. Therefore, you will see this mistake 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 sheet
Split up your requests into separate worksheets
Delete any unused tabs, rows, and columns from your worksheet
Limit the size of the information response you're requesting
Use the field editor or JMESPath filters to impress out fewer fields
Change the report style to compact or grid.

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

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

Request processed, no records constitute

This is more than of a notification than an error bulletin. Information technology ways that in that location is no effect with the setup of your API asking, just the API service returned an empty response. If you were expecting data 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 as dates and IDs
remove any JMESPath expressions as they could exist filtering out your results.

ScriptError: Authority is required to perform that action

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

Service invoked too many times for ane twenty-four hour period: urlfetch

This error message comes from Google itself. It is often, but not necessarily, associated with the IMPORTAPI custom part, every bit IMPORTAPI enables large volumes of API calls. Google has quotas on its usage, as described hither: https://developers.google.com/apps-script/guides/services/quotas. A URL Fetch call is a request to get a URL, so 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 business relationship (each email accost), and sums together all the fetch calls from all the sheets you lot're using. This includes all scripts, functions, and other add-ons that y'all may be running in add-on to API Connector. Unfortunately Google doesn't provide any breakdown of where URL fetch calls come from, or any indicator of how close you are to the limit, and so yous will need to review your sheets manually for excess URL fetch calls.

Pay special attention to functions like IMPORTJSON, GOOGLEFINANCE, and API Connector's IMPORTAPI every bit these may produce URL fetch calls every minute. Please check this commodity for data on preventing backlog recalculation.

We received an fault from xyz.com (###)

This error message occurs when the API you're trying to connect to refuses to run your asking and has returned an HTTP Response Status error code.

Starting time, click "show response" to see the exact mistake bulletin returned past the server. This will often warning you to the specific nature of the trouble.

Since these errors come from the API, non from API Connector, you may demand to check their API documentation to resolve the issue. Y'all can as well look upwardly the HTTP error lawmaking displayed within the parentheses. This site contains brief explanations for all error codes: https://httpstatuses.com.

Other

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

lyonmarn1991.blogspot.com

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