求助：Import Range脚本超时，Google脚本运行无输出触发超时错误

Hey there, let's dig into why your clone script is timing out without any output—this is a super common snag when swapping out IMPORTRANGE with Apps Script, so let's break down the likely issues and fixes:

1. Your Script Might Be Missing Core Logic (Or Inefficiently Handling Data) #

From the snippet you shared, it looks like you only initialized the source spreadsheet but didn't include the steps to fetch data or write it to a target sheet. Even if you did include those steps, inefficient cell-by-cell operations are the #1 cause of timeouts in Apps Script.

Instead of looping through individual cells, use bulk data operations to cut down on execution time. Here's a streamlined, efficient version of what your script should look like:

function cloneGoogleSheet() {
  // Initialize source and target spreadsheets
  const sourceSS = SpreadsheetApp.openById('ssA');
  const targetSS = SpreadsheetApp.openById('ssB'); // Replace with your target ID
  
  // Get specific sheets (replace with your sheet names)
  const sourceSheet = sourceSS.getSheetByName('SourceSheet');
  const targetSheet = targetSS.getSheetByName('TargetSheet');
  
  Logger.log('Fetching source data...');
  // Get only the range with actual data (avoids loading empty rows)
  const sourceData = sourceSheet.getDataRange().getValues();
  
  Logger.log('Clearing target sheet contents...');
  // Optional: Clear existing data before writing
  targetSheet.clearContents();
  
  Logger.log('Writing data to target...');
  // Write all data in one batch (way faster than single cell writes)
  targetSheet.getRange(1, 1, sourceData.length, sourceData[0].length).setValues(sourceData);
  
  SpreadsheetApp.flush();
  Logger.log('Clone completed successfully!');
}

2. You're Hitting Execution Limits (Or Permissions Issues) #

• Permissions: Make sure you authorized the script to access both your source and target spreadsheets. The first time you run it, you'll need to go through the "Advanced" authorization flow to grant access.
• Large Datasets: If your sheet has tens of thousands of rows, Apps Script's 6-minute execution limit might be too tight. For this, split the data into batches (e.g., 1000 rows at a time) and use PropertiesService to track progress between runs.

3. Debug the Silent Failure With Logs #

The best way to figure out where your script is getting stuck is to add Logger.log() statements after every key step. Then, check the execution logs (Script Editor > View > Logs) to see the last logged message—this will tell you exactly which part of the script is hanging.

4. Consider a Targeted Sync Instead of Full Clone #

If you don't need to copy the entire sheet every time, optimize by only syncing new or updated rows:

• Add a timestamp column to your source sheet that updates when a row is edited.
• In your script, fetch only rows where the timestamp is newer than the last sync time (stored in PropertiesService).

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