If you encounter service errors like this, it might be due to accessing incorrect ranges, and the error may only show up during a subsequent access. For instance, if you attempt to reference columns or rows that do not exist in your spreadsheet, such as referencing column H when you only have columns A-E, or trying to access row 10001 when you actually have only 10000 rows.

The Apps Script Issue Tracker has information on this matter: https://issuetracker.google.com/issues/68062620

Regarding the root cause of your problem, it seems that your script is not optimized and does not adhere to the best practices recommended by Google for using the Spreadsheet Service. It's advisable to utilize batch operations like the Range#setValues method to write entire blocks of data, or at least use appendRow to add rows one by one (instead of individual cell updates with

sheet.getRange(rowIndex, someColumn).setValue(oneValue)

). These methods automatically adjust the sheet to accommodate new data entries.

Here's an example modification suggested for your code:

var itemFields = [ "name",
                   "rarity",
                   "price_last_changed",
                   "max_offer_unit_price",
                   "min_sale_unit_price",
                   "offer_availability",
                   "sale_availability" ];
function addResultPage_(sheet, results) {
  const imgs = [],
  const data = results.map(function (result, index) {
    if (result.img)
      imgs.push({row: index, url: result.img});
    return itemFields.map(function (field) { return result[field] || ""; });
  });
  if (!data.length) return;

  const startRow = sheet.getLastRow() + 1;
  sheet.getRange(startRow, 2, data.length, data[0].length).setValues(data);
  if (imgs.length)
    imgs.forEach(function (imgInfo) {
      sheet.insertImage(imgInfo.url, 1, startRow + imgInfo.row);
    });
}
function listAllItems() {
  const sheet = SpreadsheetApp.getActiveSheet(),
        totalPages = updateStartStatus("List All Items");

  for (var page = 1; page <= totalPages; ++page) {
    var pageResults = getItemsByPage(page);
    if (pageResults.results)
      addResultPage_(sheet, pageResults.results);
    else
      console.warn({message: "No results for page '" + page + "'", resp: pageResults});
  }
}

I found ellockie's response helpful as I encountered a similar issue without realizing it. Initially, I attempted to sort a range using range.sort(8), but for collecting the range, I mistakenly used:

sheet.getRange(2, 1, sheet.getMaxRows(), sheet.getMaxColumns());

In hindsight, the correct approach would have been:

sheet.getRange(2, 1, sheet.getMaxRows() - 1, sheet.getMaxColumns());

As of the latest update on 5/1/2015, the error message remains vague and uninformative, displaying only "Service error: Spreadsheets".

Hey there Marchello, I faced a similar issue today and managed to find a solution by following this link: https://example.com/solution-code (check out #4). The workaround involves adding rows at the end of the spreadsheet to kickstart the script functionality once more. This approach successfully resolved my problem.

Experiencing a similar issue but managed to uncover the root problem, which turned out to be attempting to duplicate just one cell... CAN YOU IMAGINE?

A segment of the code was aimed at erasing a single row, and that stubborn cell persisted. After trying to replicate a single row and causing the entire Spreadsheet to crash, I rebooted and proceeded to copy cells individually only to realize that an empty cell triggered the crash. Removing the whole column along with other vacant columns led me through the gates of success!

Now, copying an entire row works flawlessly with the script!!!!!

My experience involved using formulas with 'dynamic' ranges like =sum(b2:b), which I recall was highlighted as a potential issue in the updated google spreadsheets.

By adjusting to sum(b2:b22) (ensuring the range stays within the sheet's final row), I was able to resolve the issue successfully.

The reason for the error in my scenario was due to me instructing a different spreadsheet to organize its data based on 25 columns, even though it only had 19 columns available.

In hindsight, I realized that I had made the mistake of deleting unnecessary columns from the spreadsheet after already writing the script to sort 25 columns instead of utilizing getLastColumn method - an error that could have been easily avoided.

One issue I encountered was the same as what ellockie pointed out: The need for dynamic range in a formula. In my situation, I previously used =INDEX(B7:B,1) to retrieve the first cell following my column header - B7. This approach was necessary because I had a script that would insert a new cell and move all existing data down. As a result, I needed a way to consistently reference the first row value regardless of cell movement. I eventually switched to using

=INDIRECT(CONCATENATE(CHARACTER(COLUMN()+64);ROW()+4))

in order to make the reference dynamic.

• CHARACTER(COLUMN()+64) provides the column letter, essentially replacing =INDEX(B7:B,1) with B
• ROW()+4 gives me the desired row number, which is 4 rows beneath where this formula resides. This replaces =INDEX(B7:B,1) with 7

I encountered a similar issue where an error started appearing during the script execution.

The error specifically mentioned that the Service Spreadsheets failed while trying to access a document with an ID.

Upon investigation, I realized that the problem stemmed from formulas referencing ranges that had been shifted.

To resolve this issue, I adjusted the affected formulas by including headers or an extra cell to ensure they remained accurate when new cells were added.

For example, in one instance, I was inserting new cells above row 5 through a script, causing my SUMIFS formulas on other sheets to sum data from row 5.

My solutions included:

1. Adding an extra cell to formulas to prevent them from being affected by new cell additions

In another scenario, I modified the SUMIFS formula to start summing from row 4 (headers) instead of row 5. This approach had worked well in the past.

During development, I inadvertently altered these formulas to reference row 4 instead of row 5, leading to the script failure in Google Sheets.

2. If the first method doesn't work, consider using the INDIRECT function instead of direct range references. This allowed me to continue using SUMIFS from row 5 without any issues.