IssueTracker

Possibly related to the behavior I was seeing here - https://issuetracker.google.com/issues/245384098 as well as this issue https://issuetracker.google.com/issues/156530211

We have a time triggered script that calls SpreadsheetApp.open(file) within a Google Drive folder iterator, and over the past few months we've been seeing random spreadsheets fail to open with one of the following error almost every single day:

Exception: Document XYZ is missing (perhaps it was deleted, or you don't have read access?)

Service Spreadsheets failed while accessing document with id XYZ

When these errors happen, I can manually open the spreadsheet referenced in the error and view/edit the spreadsheet without any issues. It only seems to affect Apps Script access to the spreadsheet. For any given spreadsheet that runs into this issue, it can last up to several hours (erroring on this same exact spreadsheet). Removing this spreadsheet from the Google Drive folder being iterated allows the script to successfully run (unless there is another spreadsheet throwing access errors).

Further, depending on the script's design, this access error can entirely break downstream functionality. And given the way the error happens (ie. it hangs on SpreadsheetApp.open(file) - possibly internally retrying to access that file, and eventually timing out), it makes creating corresponding error handling code difficult and leads to unreliable behavior.

What steps will reproduce the problem?

1. Create a function that loops through >20 spreadsheets and call SpreadsheetApp.open(file) for each. At the beginning of this function set a 'isRunning' flag set in the ScriptProperties and then clear this flag when the script finishes.
2. Create a separate function that calls the function created in Step 1, but only if the 'isRunning' flag is not set.
3. Schedule a trigger to run the function in Step 2 every 1 minute.
4. Wait for errors...

Have these errors been replicated / investigated by the Apps Script dev team? Is there any known cause of these errors?

Thanks, Dustin