The Apps Script dashboard lets you manage and monitor your Apps Script projects. You can use the dashboard to do any of the following:
- View and search for your existing Apps Script projects, including bound scripts attached to Google Workspace documents.
- Create new projects.
- View details about your projects, such as the OAuth scopes it uses.
- Monitor the health and usage of your script projects.
- View execution logs for your projects and others that run using your account's credentials.
- Toggle on or off the Apps Script API to allow or prevent apps from using the API to interact with your script projects.
View and search projects
The Apps Script dashboard lists all the script projects that you can view or edit. The left nav of the dashboard divides these projects into the following categories:
- Monitored Projects. Projects that you are monitoring.
- My Projects. Projects for which you are an owner.
- All Projects. Projects which you own or have view or edit permissions for.
- Shared with me. Projects that you do not own but that have been shared with you.
- Trash. Projects that you have removed from Google Drive.
View project details
Each project includes a view to see developer details about the project. To view the details about a project, click the row from the project list.
The project details view shows Error rate, Executions and Users data and graphs about the project, as well as OAuth scopes requested of any end-user using the project. The data metrics are defined as follows:
- Error rate. The percent of executions that failed to run due to uncaught exceptions. It is calculated as failed executions divided by the total executions over the defined time period.
- Executions. The number of times a project has been "run" or executed. See Execution types for more information about how a project can be run.
- Users. The number of unique user (accounts) who ran the project one or more times over the specified time period. Anonymous users are not tracked and therefore are not reflected in the user count or graphs.
Each deployment of your project appears as a tab on the Project Details page above the data and graphs; you can select the tab to see the associated data for that deployment. Selecting ALL shows aggregate data for all of the project's deployments and from executions resulting from developers running the project from within the Apps Script code editor.
You may have access to significantly more Apps Script projects than you use or manage on a regular basis. The Monitored Projects feature lets you bookmark the projects for easy access, while also monitoring aggregate usage and error rate statistics and graphs on those projects.
To monitor a project, click the viewing project details.menu on the right of a project row and select Start monitoring. You can also start monitoring a project by clicking the menu while
In the left nav, you can select Monitored Projects to see the projects you've bookmarked. Click the Error rate, Executions or Users scorecard at the top of this page to see the associated graphs for all your monitored projects over the last 7 days.
You can stop monitoring a project by clicking themenu in its project row and selecting Stop monitoring.
You can use the Apps Script dashboard to view and manage individual executions of Apps Script project functions. You can find a full log of recent executions by selecting the Executions item in the left nav.
The Executions panel shows by default a log of all previous and currently running executions for projects for which you are an owner, editor or viewer. This list can also include function executions in projects that you don't have access to if they run on your behalf (for example, add-ons that you've installed and run). The execution list only shows the initial function that is called to start the execution. It does not show every function that was called during that execution.
You can control which type of execution is reported in the log using the filters at the top of the view. Each row of the log represents a single execution. The Start Time, Duration, and Status columns show the corresponding information about that execution. The Logs column provides a link to the Stackdriver logs for that project.
The Function column shows the function name of the function that initiated the execution. There is no name in this column if you don't have access to the execution's corresponding script project but it ran on your behalf.
The Execution type column shows what initiated the execution. Values include:
- Add On. The execution originated from an add-on.
- Execution API. The execution originated from an invocation of the Apps Script API.
- Time Driven. The execution was caused by a time event.
- Trigger. The execution originated from a trigger source.
- Webapp. The execution originated from a deployed web app.
- Editor. The execution originated from the Apps Script editor.
Long running executions that are currently in-progress are indicated by a Status of "Running". You can stop these executions by clicking theicon in the Terminate column.
You can adjust your dashboard settings by selecting Settings in the left nav.
To access this toggle click the Google Apps Script API label in the Settings panel. This opens a new panel with warning text and a toggle switch. Access to your script projects is toggled off by default as a security precaution. Once you grant access, any third-party application you authorize can use the API to modify your scripts and deployments. You can revoke this access in the Settings panel at any time.
Find more information in the Apps Script API access guide.
If you're encountering an error or need help with using the Apps Script dashboard, you should start by searching or posting to Stack Overflow:
If you have determined that the cause of a problem is due to a bug in the dashboard itself, you can search our Issue Tracker to determine if it is a known issue. If it is, you can star the issue (click the star next to the issue number)—we prioritize bugs that receive more stars. You can also add comments to existing issues, but you should only do this if you are adding context or additional information about the problem.
If the issue is completely new, you can report it on our Issue Tracker as well. If you do, please ensure you include the following information in your bug description:
- A description of the problem, and the behavior you expected instead.
- A list of steps that can be used to reproduce the problem.
- A description of the output you expect and what actually occurred. Include any error messages you receive.
- Information about your development environment, including programming language, library versions, etc.
Be aware that issues may be relatively quiet for a while. This does not mean we will never fix an issue; it just means that there are currently no updates.
If there is a feature or functionality missing from the dashboad that you would like to have, you can search our Issue Tracker to determine if others have requested it. If it has already been requested, please star the issue (click the star next to the issue number)—we prioritize bugs that receive more stars. You can also add comments to existing issues, but you should only do this if you are adding context or additional information about the problem.
If the feature hasn't been requested yet, you can file a feature request on our Issue Tracker. Please describe the specific functionality you would like to see added, as well as reasons you think it's important. If possible, include specific details about your use case and the new opportunities the feature would allow for.