使用DocumentApp.openById()报‘Service unavailable’错误的排查求助

Hey there, let's break down why you're hitting that frustrating "Service unavailable: Docs" error when calling DocumentApp.openById(docID) and walk through fixes to get your script running smoothly.

Common Causes & Fixes #

1. You're Hitting Google Apps Script Quota Limits #

Google enforces strict quota limits for services like Docs, especially when processing multiple files in a loop. Your applyDocCopytoList() function iterates over spreadsheet rows and calls docCopy() each time—this can trigger quota restrictions if you're moving too fast.

Fix:
Add a small delay between iterations to give the API time to catch up. Even 1-2 seconds can make a huge difference. Modify your loop in applyDocCopytoList():

for (var i = 1; i < data.length; i++) {
  // ... existing code to get folderId, fileName, targetFile ...
  if(latestFileId!= undefined){
    docCopy(latestFileId, targetFile);
    Utilities.sleep(1000); // Wait 1 second between each copy operation
  }
}

You can also check your quota usage directly in the script editor: go to Resources > Cloud Platform Project > Dashboard to see if you've exceeded daily or per-minute limits.

2. Missing Permissions for the Target Document #

If the docIdTarget from your spreadsheet points to a document your script doesn't have access to (e.g., it's shared with you but not the script's runtime identity), this error will pop up.

Fix:

• Verify the target document is shared with the email linked to your script (usually your Google account email).
• Re-authorize the script manually: run the test() function directly to trigger the OAuth consent flow, and make sure you grant all requested permissions.

3. Rapid API Calls Triggering Rate Limiting #

Your docCopy() function opens both the source and target documents every time it runs. When looping through dozens of rows, this flood of API calls can trigger Google's rate limiting.

Fix:

• Optimize your code to minimize redundant calls. For example, if you're copying to the same target document multiple times, open it once outside the loop instead of every iteration.
• Split your spreadsheet rows into smaller batches and run them separately instead of processing all at once.

4. Invalid or Malformed Document IDs #

Double-check that the targetFile values in your spreadsheet are valid Google Docs IDs. If an ID is wrong, or points to a non-Docs file (like a Sheet or PDF), DocumentApp.openById() will fail.

Fix:
Add validation in your docCopy() function to catch invalid IDs early:

function docCopy(dociIdSource, docIdTarget){
  Logger.log('The file with id: ' + dociIdSource + ' will be copied to the target id: ' + docIdTarget);
  
  // Validate target document before opening
  try {
    var baseDoc = DocumentApp.openById(docIdTarget);
  } catch(e) {
    Logger.log('Failed to open target document: ' + e.message);
    return; // Skip this row if target is invalid
  }
  
  // ... rest of your copy logic ...
}

5. Temporary Google Service Outage #

Occasionally, Google's Docs service might have temporary downtime. If none of the above fixes work, check the Google Workspace Status Dashboard to rule out an ongoing platform issue.

Quick Code Cleanup Note #

I noticed a typo in your mostRecentFiIeInFolder() function name (it uses an uppercase I instead of L for "File"). While this isn't causing the current error, fixing it will make your code more maintainable long-term.

Also, the TEXT element type clause in your docCopy() function might not work as expected—TEXT elements are typically nested inside paragraphs, so you can probably remove that line without breaking your copy logic.

内容的提问来源于stack exchange，提问作者merilstack