DiscoveryVIP / Apps Script AcademyHelp

61. Triggers and automatic execution

Module 13 · 20 minutes · Lesson 60; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use triggers and automatic execution without changing the wrong data?

Predict

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

Understand

A trigger invokes a named function in response to an event or schedule. Creating a trigger is not the same as firing it. The simulator records trigger definitions and uses a separate event selector to invoke handlers. Script-driven sheet edits do not automatically fire onEdit. Avoid installing duplicate triggers each time setup runs.

Example 1: Working automation

A daily trigger definition is stored. The report handler is not executed by setup itself.

function main() {
  ScriptApp.newTrigger("dailyReport").timeBased().everyDays(1).atHour(9).create();
  console.log(ScriptApp.getProjectTriggers().length);
}
function dailyReport() { console.log("Daily report started"); }
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: ScriptApp.newTrigger("dailyReport").timeBased().everyDays(1).atHour(9).create();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 3: console.log(ScriptApp.getProjectTriggers().length);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function dailyReport() { console.log("Daily report started"); }
Define a named block of instructions. Run Script calls main; helpers run only when called.
Exact expected output and resource
{
  "logs": [
    "1"
  ],
  "error": null,
  "resource": "triggers",
  "value": [
    {
      "handler": "dailyReport",
      "type": "clock",
      "days": 1,
      "hour": 9,
      "id": "trigger-1"
    }
  ]
}

Example 2: Investigate a reproducible failure

Predict the effect of everyDays(2) and identify the first mismatch. This example is intentionally faulty.

function main() {
  ScriptApp.newTrigger("dailyReport").timeBased().everyDays(2).atHour(9).create();
  console.log(ScriptApp.getProjectTriggers().length);
}
function dailyReport() { console.log("Daily report started"); }
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: ScriptApp.newTrigger("dailyReport").timeBased().everyDays(2).atHour(9).create();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 3: console.log(ScriptApp.getProjectTriggers().length);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function dailyReport() { console.log("Daily report started"); }
Define a named block of instructions. Run Script calls main; helpers run only when called.
Exact expected output and resource
{
  "logs": [
    "1"
  ],
  "error": null,
  "resource": "triggers",
  "value": [
    {
      "handler": "dailyReport",
      "type": "clock",
      "days": 2,
      "hour": 9,
      "id": "trigger-1"
    }
  ]
}

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() {
  ScriptApp.newTrigger("dailyReport").timeBased().everyDays(1).atHour(9).create();
  console.log(ScriptApp.getProjectTriggers().length);
}
function dailyReport() { console.log("Daily report started"); }
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: ScriptApp.newTrigger("dailyReport").timeBased().everyDays(1).atHour(9).create();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 3: console.log(ScriptApp.getProjectTriggers().length);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function dailyReport() { console.log("Daily report started"); }
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: lessonAction();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
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: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "1",
    "2"
  ],
  "error": null,
  "resource": "triggers",
  "value": [
    {
      "handler": "dailyReport",
      "type": "clock",
      "days": 1,
      "hour": 9,
      "id": "trigger-1"
    },
    {
      "handler": "dailyReport",
      "type": "clock",
      "days": 1,
      "hour": 9,
      "id": "trigger-2"
    }
  ]
}

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() {
  ScriptApp.newTrigger("dailyReport").timeBased().everyDays(1).atHour(9).create();
  console.log(ScriptApp.getProjectTriggers().length);
}
function dailyReport() { console.log("Daily report started"); }
function main() {
  console.log("Start: Triggers and automatic execution");
  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: ScriptApp.newTrigger("dailyReport").timeBased().everyDays(1).atHour(9).create();
Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
Line 3: console.log(ScriptApp.getProjectTriggers().length);
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 4: }
Close the current block. Indentation makes scope and the function boundary visible.
Line 5: function dailyReport() { console.log("Daily report started"); }
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 6: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 7: console.log("Start: Triggers and automatic execution");
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 8: try { lessonAction(); console.log("Completed operation"); }
Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
Line 9: 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 10: }
Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
  "logs": [
    "Start: Triggers and automatic execution",
    "1",
    "Completed operation"
  ],
  "error": null,
  "resource": "triggers",
  "value": [
    {
      "handler": "dailyReport",
      "type": "clock",
      "days": 1,
      "hour": 9,
      "id": "trigger-1"
    }
  ]
}

Build and test

Repair the supplied script so that: A daily trigger definition is stored. The report handler is not executed by setup itself. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  ScriptApp.newTrigger("dailyReport").timeBased().everyDays(2).atHour(9).create();
  console.log(ScriptApp.getProjectTriggers().length);
}
function dailyReport() { console.log("Daily report started"); }

Graduated hints

Hint 1

Inspect the operation containing everyDays(2). Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns everyDays(1). Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses everyDays(1) where the broken source uses everyDays(2). Explain why before applying it.

Reference solution

function main() {
  ScriptApp.newTrigger("dailyReport").timeBased().everyDays(1).atHour(9).create();
  console.log(ScriptApp.getProjectTriggers().length);
}
function dailyReport() { console.log("Daily report started"); }

Explain and reflect

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

Adapt the input records and triggers output 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 triggers 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: onOpen and onEdit