55. Scheduling and reminder workflows
Module 11 · 20 minutes · Lesson 54; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use scheduling and reminder workflows without changing the wrong data?
- Explain scheduling and reminder workflows in your own words
- Trace the actual drafts state change 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
Separate schedule creation, conflict detection and communication review. A reminder draft should name the event and time clearly and not rely on a machine’s implicit time zone. Avoid sending calendar invitations from a learning fixture. The example records one event and prepares a related draft for manual review.
Example 1: Working automation
The event and draft are separate side effects. A draft failure does not automatically roll back the event.
function main() {
const start = new Date("2026-12-01T14:00:00Z");
CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
GmailApp.createDraft("alex@example.com", "Workshop reminder", "Starts " + start.toISOString());
}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 start = new Date("2026-12-01T14:00:00Z");
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: GmailApp.createDraft("alex@example.com", "Workshop reminder", "Starts " + start.toISOString());
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-2",
"to": "alex@example.com",
"subject": "Workshop reminder",
"body": "Starts 2026-12-01T14:00:00.000Z",
"htmlBody": ""
}
]
}Example 2: Investigate a reproducible failure
Predict the effect of "invalid" and identify the first mismatch. This example is intentionally faulty.
function main() {
const start = new Date("2026-12-01T14:00:00Z");
CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
GmailApp.createDraft("invalid", "Workshop reminder", "Starts " + start.toISOString());
}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 start = new Date("2026-12-01T14:00:00Z");
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: GmailApp.createDraft("invalid", "Workshop reminder", "Starts " + start.toISOString());
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [],
"error": "Invalid simulated recipient.",
"resource": "drafts",
"value": []
}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 start = new Date("2026-12-01T14:00:00Z");
CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
GmailApp.createDraft("alex@example.com", "Workshop reminder", "Starts " + start.toISOString());
}
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 start = new Date("2026-12-01T14:00:00Z");
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: GmailApp.createDraft("alex@example.com", "Workshop reminder", "Starts " + start.toISOString());
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
- 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": [],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-2",
"to": "alex@example.com",
"subject": "Workshop reminder",
"body": "Starts 2026-12-01T14:00:00.000Z",
"htmlBody": ""
},
{
"id": "draft-4",
"to": "alex@example.com",
"subject": "Workshop reminder",
"body": "Starts 2026-12-01T14:00:00.000Z",
"htmlBody": ""
}
]
}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 start = new Date("2026-12-01T14:00:00Z");
CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
GmailApp.createDraft("alex@example.com", "Workshop reminder", "Starts " + start.toISOString());
}
function main() {
console.log("Start: Scheduling and reminder workflows");
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 start = new Date("2026-12-01T14:00:00Z");
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 4: GmailApp.createDraft("alex@example.com", "Workshop reminder", "Starts " + start.toISOString());
- Call the named Workspace service. Locally this invokes a documented adapter; in Google it may require authorization and create persistent changes.
- Line 5: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 6: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 7: console.log("Start: Scheduling and reminder workflows");
- 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: Scheduling and reminder workflows",
"Completed operation"
],
"error": null,
"resource": "drafts",
"value": [
{
"id": "draft-2",
"to": "alex@example.com",
"subject": "Workshop reminder",
"body": "Starts 2026-12-01T14:00:00.000Z",
"htmlBody": ""
}
]
}Build and test
Repair the supplied script so that: The event and draft are separate side effects. A draft failure does not automatically roll back the event. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const start = new Date("2026-12-01T14:00:00Z");
CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
GmailApp.createDraft("invalid", "Workshop reminder", "Starts " + start.toISOString());
}Graduated hints
Hint 1
Inspect the operation containing "invalid". Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns "alex@example.com". Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses "alex@example.com" where the broken source uses "invalid". Explain why before applying it.
Reference solution
function main() {
const start = new Date("2026-12-01T14:00:00Z");
CalendarApp.getDefaultCalendar().createEvent("Workshop", start, new Date("2026-12-01T15:00:00Z"));
GmailApp.createDraft("alex@example.com", "Workshop reminder", "Starts " + start.toISOString());
}Explain and reflect
Which operation proves the intended result in scheduling and reminder workflows? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the input records and drafts 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 drafts 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.