90. Quotas, batching, locks and duplicate processing
Module 18 · 20 minutes · Lesson 89; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use quotas, batching, locks and duplicate processing without changing the wrong data?
- Explain quotas, batching, locks and duplicate processing in your own words
- Trace the actual sheets 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
Quotas vary by service and account and can change. Use current official limits, not a permanent number copied into a lesson. Batch reads and writes reduce explicit service calls; count operations rather than inventing Google timings. Locks coordinate cooperating executions. Keep a stable processing key so retries do not duplicate side effects.
Example 1: Working automation
The lock is released in finally. The processing marker is written only after the intended cell write succeeds.
function main() {
const lock = LockService.getScriptLock();
if (!lock.tryLock(1000)) throw new Error("Another run is active");
try {
const settings = PropertiesService.getScriptProperties();
if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Complete");
settings.setProperty("processed:R1", "yes");
console.log("Processed R1");
} finally { lock.releaseLock(); }
}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 lock = LockService.getScriptLock();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: if (!lock.tryLock(1000)) throw new Error("Another run is active");
- Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
- Line 4: try {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const settings = PropertiesService.getScriptProperties();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 6: if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Complete");
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 8: settings.setProperty("processed:R1", "yes");
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 9: console.log("Processed R1");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 10: } finally { lock.releaseLock(); }
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 11: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Processed R1"
],
"error": null,
"resource": "sheets",
"value": {
"People": [
[
"Name",
"Status"
],
[
"Alex",
"Complete"
],
[
"Jordan",
"Pending"
],
[
"Morgan",
"Pending"
]
],
"Sales": [
[
"Customer",
"Amount",
"Approved"
],
[
"Alex",
120,
true
],
[
"Jordan",
80,
false
],
[
"Morgan",
200,
true
]
],
"Tasks": [
[
"Task",
"Status"
],
[
"Review invoice",
"Open"
],
[
"Publish report",
"Complete"
]
]
}
}Example 2: Investigate a reproducible failure
Predict the effect of setValue("Wrong") and identify the first mismatch. This example is intentionally faulty.
function main() {
const lock = LockService.getScriptLock();
if (!lock.tryLock(1000)) throw new Error("Another run is active");
try {
const settings = PropertiesService.getScriptProperties();
if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Wrong");
settings.setProperty("processed:R1", "yes");
console.log("Processed R1");
} finally { lock.releaseLock(); }
}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 lock = LockService.getScriptLock();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: if (!lock.tryLock(1000)) throw new Error("Another run is active");
- Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
- Line 4: try {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const settings = PropertiesService.getScriptProperties();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 6: if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Wrong");
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 8: settings.setProperty("processed:R1", "yes");
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 9: console.log("Processed R1");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 10: } finally { lock.releaseLock(); }
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 11: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Processed R1"
],
"error": null,
"resource": "sheets",
"value": {
"People": [
[
"Name",
"Status"
],
[
"Alex",
"Wrong"
],
[
"Jordan",
"Pending"
],
[
"Morgan",
"Pending"
]
],
"Sales": [
[
"Customer",
"Amount",
"Approved"
],
[
"Alex",
120,
true
],
[
"Jordan",
80,
false
],
[
"Morgan",
200,
true
]
],
"Tasks": [
[
"Task",
"Status"
],
[
"Review invoice",
"Open"
],
[
"Publish report",
"Complete"
]
]
}
}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 lock = LockService.getScriptLock();
if (!lock.tryLock(1000)) throw new Error("Another run is active");
try {
const settings = PropertiesService.getScriptProperties();
if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Complete");
settings.setProperty("processed:R1", "yes");
console.log("Processed R1");
} finally { lock.releaseLock(); }
}
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 lock = LockService.getScriptLock();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: if (!lock.tryLock(1000)) throw new Error("Another run is active");
- Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
- Line 4: try {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const settings = PropertiesService.getScriptProperties();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 6: if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Complete");
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 8: settings.setProperty("processed:R1", "yes");
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 9: console.log("Processed R1");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 10: } finally { lock.releaseLock(); }
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 11: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 12: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 13: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 14: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 15: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Processed R1",
"Already processed"
],
"error": null,
"resource": "sheets",
"value": {
"People": [
[
"Name",
"Status"
],
[
"Alex",
"Complete"
],
[
"Jordan",
"Pending"
],
[
"Morgan",
"Pending"
]
],
"Sales": [
[
"Customer",
"Amount",
"Approved"
],
[
"Alex",
120,
true
],
[
"Jordan",
80,
false
],
[
"Morgan",
200,
true
]
],
"Tasks": [
[
"Task",
"Status"
],
[
"Review invoice",
"Open"
],
[
"Publish report",
"Complete"
]
]
}
}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 lock = LockService.getScriptLock();
if (!lock.tryLock(1000)) throw new Error("Another run is active");
try {
const settings = PropertiesService.getScriptProperties();
if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Complete");
settings.setProperty("processed:R1", "yes");
console.log("Processed R1");
} finally { lock.releaseLock(); }
}
function main() {
console.log("Start: Quotas, batching, locks and duplicate processing");
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 lock = LockService.getScriptLock();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: if (!lock.tryLock(1000)) throw new Error("Another run is active");
- Reject the current operation with an explicit error instead of silently continuing on invalid assumptions.
- Line 4: try {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 5: const settings = PropertiesService.getScriptProperties();
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 6: if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Complete");
- Resolve the current workbook. A real standalone project needs openById with a configured ID instead.
- Line 8: settings.setProperty("processed:R1", "yes");
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 9: console.log("Processed R1");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 10: } finally { lock.releaseLock(); }
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 11: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 12: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 13: console.log("Start: Quotas, batching, locks and duplicate processing");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 14: try { lessonAction(); console.log("Completed operation"); }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 15: 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 16: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Start: Quotas, batching, locks and duplicate processing",
"Processed R1",
"Completed operation"
],
"error": null,
"resource": "sheets",
"value": {
"People": [
[
"Name",
"Status"
],
[
"Alex",
"Complete"
],
[
"Jordan",
"Pending"
],
[
"Morgan",
"Pending"
]
],
"Sales": [
[
"Customer",
"Amount",
"Approved"
],
[
"Alex",
120,
true
],
[
"Jordan",
80,
false
],
[
"Morgan",
200,
true
]
],
"Tasks": [
[
"Task",
"Status"
],
[
"Review invoice",
"Open"
],
[
"Publish report",
"Complete"
]
]
}
}Build and test
Repair the supplied script so that: The lock is released in finally. The processing marker is written only after the intended cell write succeeds. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const lock = LockService.getScriptLock();
if (!lock.tryLock(1000)) throw new Error("Another run is active");
try {
const settings = PropertiesService.getScriptProperties();
if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Wrong");
settings.setProperty("processed:R1", "yes");
console.log("Processed R1");
} finally { lock.releaseLock(); }
}Graduated hints
Hint 1
Inspect the operation containing setValue("Wrong"). Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns setValue("Complete"). Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses setValue("Complete") where the broken source uses setValue("Wrong"). Explain why before applying it.
Reference solution
function main() {
const lock = LockService.getScriptLock();
if (!lock.tryLock(1000)) throw new Error("Another run is active");
try {
const settings = PropertiesService.getScriptProperties();
if (settings.getProperty("processed:R1")) { console.log("Already processed"); return; }
SpreadsheetApp.getActiveSpreadsheet().getActiveSheet().getRange("B2").setValue("Complete");
settings.setProperty("processed:R1", "yes");
console.log("Processed R1");
} finally { lock.releaseLock(); }
}Explain and reflect
Which operation proves the intended result in quotas, batching, locks and duplicate processing? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the input records and sheets 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 sheets 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.