

This is only possible if your script projectĮxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. Make the most of Cloud Logging and error reporting you must have access You can view a simplified version of Cloud logs in the There are no requirements for using the built-in execution log. No setup is required beyondĮnabling exception logging. Your script has not yet logged any exceptions. If you are prompted to "Set up Error Reporting" this is because View your Cloud error reports in the GCP console. At the top, click File > Project properties > Info > Log exceptions.Įxception logging automatically integrates withĪ service that aggregates and displays errors produced in your script.Open the script project in the script editor.Select the Log uncaught exceptions to Cloud Operations checkbox.At the left, click Project Settings settings.To Cloud Logging, along with a stack trace. Exception loggingĮxception logging sends unhandled exceptions in your script project code When reporting issues to help you identify the relevant logs. Then users may choose to include their keys One way to use this method is to display the key to the user

You can also get the temporary active user key by calling Select a log entry of interest and expand it to view

Once you've opened the GCP project in the console, You can do this only if your script project is using a

To find temporary active user keys in your Cloud Log entries,
