Too Many Phone Calls Scheduled by This Account. Please Wait and Try Again Later.

Even the about experienced programmer rarely writes code correctly on the offset try, making troubleshooting an important function of the evolution procedure. In this section we'll comprehend some techniques that tin help you find, empathise, and debug errors in your scripts.

Fault letters

When your script encounters an mistake, an error message is displayed. The bulletin is accompanied past a line number used for troubleshooting. There are two basic types of errors displayed in this manner: syntax errors and runtime errors.

Syntax errors

Syntax errors are acquired by writing code that doesn't follow the JavaScript grammar, and the errors are detected as before long as you try to salvage the script. For example, the following code snippet contains a syntax error:

          function emailDataRow(rowNumber) {   var sheet = SpreadsheetApp.getActiveSheet();   var data = sheet.getDataRange().getValues();   var rowData = data[rowNumber-1].join(" ";   MailApp.sendEmail('john@example.com',                     'Information in row ' + rowNumber,                     rowData); }                  

The syntax problem hither is a missing ) character at the finish of the fourth line. When you try to save the script y'all'll get the post-obit fault:

Missing ) after argument list. (line 4)

These types of errors are usually uncomplicated to troubleshoot, since they are found right away and typically have simple causes. You aren't able to salve a file that contains syntax errors, meaning that simply valid code is saved into your project.

Runtime errors

These errors are caused by using a role or class incorrectly, and can only be detected once the script has been run. For example, the following lawmaking causes a runtime error:

          part emailDataRow(rowNumber) {   var sheet = SpreadsheetApp.getActiveSheet();   var data = canvass.getDataRange().getValues();   var rowData = information[rowNumber-i].join(" ");   MailApp.sendEmail('john',                     'Data in row ' + rowNumber,                     rowData); }                  

The code is formatted correctly, but we are passing the value "john" for the email address when calling MailApp.sendEmail. Since this is not a valid electronic mail address the following error is thrown when running the script:

Invalid email: john (line v)

What makes these errors more than challenging to troubleshoot is that often the data you lot are passing into a function is not written in the code, just instead pulled from a spreadsheet, form, or other external data source. Using the debugging techniques beneath can help you to identify the crusade of these errors.

Common errors

Below is a listing of common errors and their causes.

Service invoked too many times: <action name>

This error indicates that you have exceeded your daily quota for a given action. For case, you might meet this error if you send too many emails in a single twenty-four hour period. The quotas are ready at different levels for consumer, domain, and premier accounts and are subject to change at any time without a prior announcement past Google. You tin view the quota limits for various actions in the Apps Script quota documentation.

Server not available. or Server error occurred, please try again.

There are a few possible causes for these errors:

• A Google server or system is temporarily unavailable. Await for a few moments and try running the script again.
• There is an fault in your script that doesn't have a respective error message. Effort debugging your script and run across if you can isolate the problem.
• There is a problems in Google Apps Script that is causing this error. For instructions on searching for and filing issues reports, see the Bugs. Before filing a new bug, search to see if others have already reported information technology.

This error indicates that the script is lacking the dominance needed to run. When a script is run in the Script Editor or from a custom carte detail an authorization dialog is presented to the user. Nevertheless, when a script is run from a trigger, embedded with a Google Sites folio, or run as a service, the dialog cannot be presented and this error is shown.

To authorize the script, open the Script Editor and run any part. The authority prompt appears then you can authorize the script project. If the script contains new unauthorized services, you must re-authorize the script.

This fault is frequently acquired by triggers that are firing before the user has authorized them. If y'all don't have admission to the script projection (because the error is occurring for an add together-on you use, for instance), you can normally qualify the script by using the add-on over again. If a trigger continues to fire and crusade this error, you tin remove your triggers by doing the following:

New editor

1. At the left of the Apps Script project, click Triggers .
2. At the correct of the trigger yous desire to remove, click More than > Delete trigger.

Legacy editor

1. Select Edit > All your triggers in the Apps Script editor. The resulting dialog shows all active triggers running on your business relationship.
2. Find the offending trigger in the list.
3. Click the icon next to the trigger name to remove it.
4. Click Save to record the deletion.

You can also remove problematic add together-on triggers past uninstalling the add-on.

Access denied: DriveApp or The domain policy has disabled third-party Drive apps

Administrators of Google Workspace domains accept the ability to disable the Bulldoze SDK for their domain, which prevents their users from installing and using Google Drive apps. This setting also prevents the users from being able to use Apps Script add-ons that use the Bulldoze service or Advanced Bulldoze Service (even if the script was authorized prior to the admin disabling Bulldoze SDK).

Still, if an addition or spider web app using the Bulldoze service is published for domain-wide installation and is installed by the administrator for some or all users in the domain, the script functions for those users even if the Bulldoze SDK is disabled in the domain.

The script does not have permission to get the active user's identity.

Indicates that the active user'south identity and email are non available to the script. This warning results from a call to Session.getActiveUser(). It can besides result from a phone call to Session.getEffectiveUser() if the script is running in an potency mode other than AuthMode.Total. If this warning is signaled, subsequent calls to User.getEmail() only render "".

There are a number of ways to troubleshoot this warning, depending on the authorization mode the script is running under. The authorization way is exposed in triggered functions as the authMode belongings of the due east outcome parameter.

• In AuthMode.Full, consider using Session.getEffectiveUser() instead.
• In AuthMode.Limited, ensure that the owner has authorized the script.
• In other authorization modes, avert calling either method.
• If you are a Google Workspace client newly experiencing this warning from an installable trigger, ensure that the trigger is running as a user within your arrangement.

Library is missing

If you add a pop library to your script, you lot might receive an fault message stating that information technology'southward missing, fifty-fifty though the library is listed equally a dependency for your script. The reason might exist that too many people are accessing the library at the same fourth dimension. To avoid this error, endeavour one of the following solutions:

• Re-create and paste the library's code into your script and remove the library dependency.
• Copy the library script and deploy information technology as a library from your account. Be sure to update the dependency in your original script to the new library instead of the public one.

Debugging

Not all mistakes cause an error message to be displayed. In that location might be a more than subtle error where the code is technically right and can execute, simply the results are not what y'all expect. Hither are some strategies for handling such situations and farther investigating a script that is not running the mode you expect.

Logging

While debugging it's often helpful to record information equally a script project executes. Google Apps Script has two methods for logging information: the Deject logging service and the more bones Logger and console services that are congenital in to the Apps Script editor.

See the Logging guide for more details.

Error Reporting

Exceptions that occur considering of runtime errors are automatically recorded using the Google Cloud Error Reporting service. This service lets you search and filter exception messages your script project creates.

New editor

To admission Mistake Reporting, see View Cloud logs and error reports in the Google Cloud Platform console.

Legacy editor

You lot tin enable Fault Reporting the starting time time you select View > Stackdriver Logging or View > Stackdriver Error Reporting in a new script.

Once enabled, exceptions that occur considering of runtime errors are automatically recorded using the Google Cloud Stackdriver service. This service lets y'all search and filter exception letters your script projection creates. You can attain the Stackdriver Mistake Reporting interface by selecting View > Stackdriver Error Reporting in the Apps Script editor.

Executions

New editor

Every time you run a script, Apps Script makes a record of the execution, including the Deject logs. These records can help you understand which actions your script performed.

To view the executions of your script in the Apps Script projection, at the left, click Executions .

Legacy editor

Every time yous run a script, Apps Script makes a record of the execution, including the Cloud logs. These records tin can help you to understand which actions your script performed. To view the executions of your script, select View > Executions in the Apps Script editor. This opens the Executions panel for the script in the Apps Script dashboard.

Checking Apps Script service condition

Although rare, sometimes specific Google Workspace services (such as Gmail or Bulldoze) encounter temporary problems that can atomic number 82 to service outages. When this occurs, Apps Script projects that interact with these services may not office as expected.

You can check if in that location is a Google Workspace service outage by viewing the Google Workspace Status Dashboard. If an outage is currently being experienced, yous either wait for information technology to be resolved or seek additional help in the Google Workspace Assist Center or the Google Workspace Known Problems documentation.

Utilise the debugger and breakpoints

To locate bug in your script, you tin can run it in debug mode. When run in debug style, a script pauses when it hits a breakpoint, which is a line y'all've highlighted in your script that you think may take a problem. When a script pauses it displays the value of each variable at that bespeak in time, allowing y'all to inspect the inner workings of a script without having to add a lot of logging statements.

Add a breakpoint

New editor

To add a breakpoint, hover over the line number of the line you want to add the breakpoint to. At the left of the line number, click the circumvolve. The below prototype shows an instance of a breakpoint added to a script:

Legacy editor

To add a breakpoint click on the line number for the line you want to intermission at.

Run a script in debug way

New editor

To run the script in debug mode, at the tiptop of the editor click Debug.

Before the script runs the line with the breakpoint it pauses and displays a table of debug information. Y'all tin use this table to inspect data similar the values of parameters and the data stored in objects.

To control how the script is run, at the height of the Debugger console, utilize the "Footstep in", "Footstep over", and "Step out" buttons. These let yous run the script 1 line at a time and audit how values change over fourth dimension.

Legacy editor

To run the script in debug way, click the bug icon () in the toolbar. Before the script runs the line with the breakpoint it pauses and displays a table of debug information.

This table allows you lot to inspect the values of the parameters like row and electronic mail, as well as the information stored in the data object. Notice that the rowData variable doesn't have a value assigned however, because the script paused before that line was executed.

When the script is paused, an extra set up of buttons are displayed in the toolbar which let y'all to control how the script is run. Using the "step in", "step over", and "step out" buttons you can run the script one line at a fourth dimension, allowing you to inspect how values change over time.

Issues with multiple Google Accounts

If you're logged into multiple Google Accounts at the same time, you might have problem accessing your Apps Script projects, add-ons, and spider web apps. Multi-login, or existence logged into multiple Google Accounts at one time, isn't supported for Apps Script, add together-ons, or web apps.

To fix problems from multi-login, effort 1 of the following solutions:

• Log out of all your Google Accounts and merely log in to the one that has the Apps Script project, add together-on, or web app you need to access.
• Open an incognito window in Google Chrome, or an equivalent private browsing window, and log in to the Google Business relationship that has the Apps Script project, improver, or web app you need to access.

Getting aid

Debugging a problem using the tools and techniques listed above can solve a variety of bug, simply there may be bug you run into that require some extra help to solve. Run across our Support page for information on where to ask questions and file bugs.

stewartmilive.blogspot.com

Source: https://developers.google.com/apps-script/guides/support/troubleshooting

Share this post