Fixed
Status Update
No update yet.
Comments
uc...@google.com
Hello,
Thank you for the details. This has been forwarded internally.
Best regards
cl...@gmail.com
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.
ch...@google.com
sm...@google.com
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
AI-192.5587.17.36.5787298, JRE 1.8.0_202-release-1483-b49-5587405x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14.6, screens 1680x1050; Retina
AS: 3.6 Canary 6; Kotlin plugin: 1.3.41-release-Studio3.6-1; Android Gradle Plugin: (plugin information not found); Gradle: 5.5.1; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: LLDB 3.1 (revision: 3.1.4508709); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: (not found)
IMPORTANT: Please read
I'm unable to sync the project since updating to 3.6 Canary 6. According the log (attached) it seems like an issue with the Kotlin plugin.