42. Messages and threads
Module 9 · 20 minutes · Lesson 41; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use messages and threads without changing the wrong data?
- Explain messages and threads in your own words
- Trace the actual console result from the source
- Repair the supplied failing operation and verify the result
Predict
Which values or resources will change, and which should stay unchanged? Write your prediction before execution.
Understand
A Gmail search returns threads, each containing messages. Processing only the first message is a deliberate choice, not a description of every thread. Preserve sender and subject as untrusted input when rendering. The simulator models one message per sample thread and does not parse attachments.
Example 1: Working automation
The known matching thread provides sender and body; indexing an empty match list fails.
function main() {
const threads = GmailApp.search("Invoice");
const message = threads[0].getMessages()[0];
console.log(message.getFrom());
console.log(message.getPlainBody());
}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 threads = GmailApp.search("Invoice");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const message = threads[0].getMessages()[0];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: console.log(message.getFrom());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: console.log(message.getPlainBody());
- 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": [
"alex@example.com",
"Please send my invoice."
],
"error": null,
"resource": "logs",
"value": null
}Example 2: Investigate a reproducible failure
Predict the effect of GmailApp.search("No match") and identify the first mismatch. This example is intentionally faulty.
function main() {
const threads = GmailApp.search("No match");
const message = threads[0].getMessages()[0];
console.log(message.getFrom());
console.log(message.getPlainBody());
}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 threads = GmailApp.search("No match");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const message = threads[0].getMessages()[0];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: console.log(message.getFrom());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: console.log(message.getPlainBody());
- 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": "Cannot read properties of undefined (reading 'getMessages')",
"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 threads = GmailApp.search("Invoice");
const message = threads[0].getMessages()[0];
console.log(message.getFrom());
console.log(message.getPlainBody());
}
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 threads = GmailApp.search("Invoice");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const message = threads[0].getMessages()[0];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: console.log(message.getFrom());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: console.log(message.getPlainBody());
- 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": [
"alex@example.com",
"Please send my invoice.",
"alex@example.com",
"Please send my invoice."
],
"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 threads = GmailApp.search("Invoice");
const message = threads[0].getMessages()[0];
console.log(message.getFrom());
console.log(message.getPlainBody());
}
function main() {
console.log("Start: Messages and threads");
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 threads = GmailApp.search("Invoice");
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 3: const message = threads[0].getMessages()[0];
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 4: console.log(message.getFrom());
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: console.log(message.getPlainBody());
- 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: Messages and threads");
- 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: Messages and threads",
"alex@example.com",
"Please send my invoice.",
"Completed operation"
],
"error": null,
"resource": "logs",
"value": null
}Build and test
Repair the supplied script so that: The known matching thread provides sender and body; indexing an empty match list fails. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const threads = GmailApp.search("No match");
const message = threads[0].getMessages()[0];
console.log(message.getFrom());
console.log(message.getPlainBody());
}Graduated hints
Hint 1
Inspect the operation containing GmailApp.search("No match"). Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns GmailApp.search("Invoice"). Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses GmailApp.search("Invoice") where the broken source uses GmailApp.search("No match"). Explain why before applying it.
Reference solution
function main() {
const threads = GmailApp.search("Invoice");
const message = threads[0].getMessages()[0];
console.log(message.getFrom());
console.log(message.getPlainBody());
}Explain and reflect
Which operation proves the intended result in messages and threads? 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.