Fixed
Status Update
Comments
ch...@google.com <ch...@google.com>
jr...@squareup.com <jr...@squareup.com> #2
Hello,
Thank you for the details. This has been forwarded internally.
Best regards
ch...@google.com <ch...@google.com> #3
Hi,
Same here. We have a set-up running which is far below the quota, but on certain occasions it fails when accessing a document with the same error message: "service spreadsheets timed out while accessing document with id".
While normally happening only once in a while, for the last weekend it has been happening on every occasion of it running, which is every hour, so for the last 40+ times of it running it has thrown an error.
For me it fails most often on this row:
spreadsheetApp.openById("...").getSheetByName("name").getRange(1,1, sheet.getLastRow().createTextFinder("...").matchCase(false).findNext();
It would be very helpful if this could be investigated!
Thanks.
Same here. We have a set-up running which is far below the quota, but on certain occasions it fails when accessing a document with the same error message: "service spreadsheets timed out while accessing document with id".
While normally happening only once in a while, for the last weekend it has been happening on every occasion of it running, which is every hour, so for the last 40+ times of it running it has thrown an error.
For me it fails most often on this row:
spreadsheetApp.openById("...").getSheetByName("name").getRange(1,1, sheet.getLastRow().createTextFinder("...").matchCase(false).findNext();
It would be very helpful if this could be investigated!
Thanks.
jr...@squareup.com <jr...@squareup.com> #4
I think this is a V8 Runtime issue. I disabled V8 Runtime early last week and I haven't had this issue since. V8 is technically still in BETA and I've posted a seperate bug previously regarding specifically the V8 Runtime in which Google was able to replicate and is currently working on a fix
EDIT: The error happened again this morning (May 22nd) and the code ran on the previous runtime enviornment. So this bug is not specific to the V8 runtime enviornment
EDIT: The error happened again this morning (May 22nd) and the code ran on the previous runtime enviornment. So this bug is not specific to the V8 runtime enviornment
Description
- Download blocks sync.
- Missing source or javadoc artifact are redownloaded on every sync.
We should do this on the Studio side where we can do this post-sync and only re-attempt download daily (or on some other time interval