DiscoveryVIP / Apps Script AcademyHelp

5. Execution logs and authorization

Module 1 · 20 minutes · Lesson 4; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use execution logs and authorization without changing the wrong data?

Predict

Which values or resources will change, and which should stay unchanged? Write your prediction before execution.

Understand

Authorization is permission granted for a script to use services on someone’s behalf. Console messages do not grant access. A successful log is not proof that every external side effect succeeded. Inspect state and exceptions as well. The simulation never requests Google authorization. In a real project inspect the requested scopes, the account and the code before approving access; organization administrators can restrict services.

Example 1: Working automation

The normal sequence reaches Finished. An exception interrupts subsequent statements; it is not a Google authorization dialog.

function main() {
  console.log("Starting");
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  console.log(sheet.getName());
  console.log("Finished");
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log("Starting");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 4: console.log(sheet.getName());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: console.log("Finished");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Starting",
    "People",
    "Finished"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 2: Investigate a reproducible failure

Predict the effect of throw new Error("Permission scenario: inspect access"); and identify the first mismatch. This example is intentionally faulty.

function main() {
  console.log("Starting");
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  console.log(sheet.getName());
  throw new Error("Permission scenario: inspect access");
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log("Starting");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 4: console.log(sheet.getName());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: throw new Error("Permission scenario: inspect access");
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Starting",
    "People"
  ],
  "error": "Permission scenario: inspect access",
  "resource": "logs",
  "value": null
}

Example 3: Separate setup from execution and inspect repeat behavior

Call the same named operation twice. Compare outputs and resource counts to learn whether this operation is idempotent. Repeated creation is deliberately visible; real exports require a rerun policy.

function lessonAction() {
  console.log("Starting");
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  console.log(sheet.getName());
  console.log("Finished");
}
function main() {
  lessonAction();
  lessonAction();
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log("Starting");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 4: console.log(sheet.getName());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: console.log("Finished");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 7: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 8: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 9: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 10: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Starting",
    "People",
    "Finished",
    "Starting",
    "People",
    "Finished"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 4: Add a diagnostic boundary around the operation

Observe start, successful completion or a rethrown failure. This optional professional pattern adds error context without swallowing the error or rolling back changes.

function lessonAction() {
  console.log("Starting");
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  console.log(sheet.getName());
  console.log("Finished");
}
function main() {
  console.log("Start: Execution logs and authorization");
  try { lessonAction(); console.log("Completed operation"); }
  catch(error) { console.error("Failed operation: " + error.message); throw error; }
}
Important line explanations
Line 1: function lessonAction() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: console.log("Starting");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 3: const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
Line 4: console.log(sheet.getName());
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 5: console.log("Finished");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 6: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 7: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 8: console.log("Start: Execution logs and authorization");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 9: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 10: catch(error) { console.error("Failed operation: " + error.message); throw error; }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 11: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: Execution logs and authorization",
    "Starting",
    "People",
    "Finished",
    "Completed operation"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Build and test

Repair the supplied script so that: The normal sequence reaches Finished. An exception interrupts subsequent statements; it is not a Google authorization dialog. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  console.log("Starting");
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  console.log(sheet.getName());
  throw new Error("Permission scenario: inspect access");
}

Graduated hints

Hint 1

Inspect the operation containing throw new Error("Permission scenario: inspect access");. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns console.log("Finished");. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses console.log("Finished"); where the broken source uses throw new Error("Permission scenario: inspect access");. Explain why before applying it.

Reference solution

function main() {
  console.log("Starting");
  const sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  console.log(sheet.getName());
  console.log("Finished");
}

Explain and reflect

Which operation proves the intended result in execution logs and authorization? Which wrong input would expose a weakness, and what would remain unchanged?

Adapt the calculation or validation to a second realistic case. Write its expected result before running. Demonstrate one invalid case and explain whether the side effects should be rolled back or retried.

Troubleshooting

If the console is empty, inspect the logs preview: this script may work through state changes. If the function is missing, select main. For a service error inspect the first failed timeline entry and its arguments. Use Manual unless investigating a trigger. Changing input data also changes the expected result; restore sample data before the authored checks.

Knowledge check

Explain the key method or operator. Give an exact output for a second input, plus one invalid case. Verify the result in the interactive lesson; written explanations need self or educator review.

Optional AI practice

Explain this concept using the source above. Help implement one small extension and define its tests. Review/debug the source using its actual expected output; cite real method references and never claim execution.

Transfer to Google and authorization guide

Next lesson: Variables, let and const