DiscoveryVIP / Apps Script AcademyHelp

86. Syntax, runtime and logic errors

Module 18 · 20 minutes · Lesson 85; earlier service and JavaScript fundamentals

Open Interactive Lesson

Discover

How can you use syntax, runtime and logic errors without changing the wrong data?

Predict

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

Understand

Syntax errors prevent parsing, runtime errors interrupt execution, and logic errors can produce plausible but wrong results. Successful execution is not sufficient evidence. Write an independent expected result and compare it. The repair exercise introduces a logic error that throws only when the explicit assertion detects it.

Example 1: Working automation

The assertion catches a wrong sign even though both arithmetic expressions are syntactically valid.

function main() {
  const expected = 80;
  const actual = 100 * (1 - 0.2);
  if (actual !== expected) throw new Error("Discount regression: " + actual);
  console.log("Discount verified");
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const expected = 80;
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: const actual = 100 * (1 - 0.2);
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 4: if (actual !== expected) throw new Error("Discount regression: " + actual);
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 5: console.log("Discount verified");
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": [
    "Discount verified"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Example 2: Investigate a reproducible failure

Predict the effect of 1 + 0.2 and identify the first mismatch. This example is intentionally faulty.

function main() {
  const expected = 80;
  const actual = 100 * (1 + 0.2);
  if (actual !== expected) throw new Error("Discount regression: " + actual);
  console.log("Discount verified");
}
Important line explanations
Line 1: function main() {
Define a named block of instructions. Run Script calls main; helpers run only when called.
Line 2: const expected = 80;
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: const actual = 100 * (1 + 0.2);
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 4: if (actual !== expected) throw new Error("Discount regression: " + actual);
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 5: console.log("Discount verified");
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": [],
  "error": "Discount regression: 120",
  "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() {
  const expected = 80;
  const actual = 100 * (1 - 0.2);
  if (actual !== expected) throw new Error("Discount regression: " + actual);
  console.log("Discount verified");
}
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: const expected = 80;
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: const actual = 100 * (1 - 0.2);
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 4: if (actual !== expected) throw new Error("Discount regression: " + actual);
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 5: console.log("Discount verified");
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": [
    "Discount verified",
    "Discount verified"
  ],
  "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() {
  const expected = 80;
  const actual = 100 * (1 - 0.2);
  if (actual !== expected) throw new Error("Discount regression: " + actual);
  console.log("Discount verified");
}
function main() {
  console.log("Start: Syntax, runtime and logic errors");
  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: const expected = 80;
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 3: const actual = 100 * (1 - 0.2);
Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
Line 4: if (actual !== expected) throw new Error("Discount regression: " + actual);
Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
Line 5: console.log("Discount verified");
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: Syntax, runtime and logic errors");
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: Syntax, runtime and logic errors",
    "Discount verified",
    "Completed operation"
  ],
  "error": null,
  "resource": "logs",
  "value": null
}

Build and test

Repair the supplied script so that: The assertion catches a wrong sign even though both arithmetic expressions are syntactically valid. Preserve other source data. Checks compare observable output and the named resource, not exact source text.

function main() {
  const expected = 80;
  const actual = 100 * (1 + 0.2);
  if (actual !== expected) throw new Error("Discount regression: " + actual);
  console.log("Discount verified");
}

Graduated hints

Hint 1

Inspect the operation containing 1 + 0.2. Compare it with the stated rule and the first mismatch.

Hint 2

The repair concerns 1 - 0.2. Change only the relevant argument, operator or method; rerun with fresh input.

Hint 3

The reference uses 1 - 0.2 where the broken source uses 1 + 0.2. Explain why before applying it.

Reference solution

function main() {
  const expected = 80;
  const actual = 100 * (1 - 0.2);
  if (actual !== expected) throw new Error("Discount regression: " + actual);
  console.log("Discount verified");
}

Explain and reflect

Which operation proves the intended result in syntax, runtime and logic errors? 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: Logs and failure investigation