Fixed
Status Update
Comments
me...@thomaskeller.biz <me...@thomaskeller.biz> #2
Hello,
Thank you for the details. This has been forwarded internally.
Best regards
uc...@google.com <uc...@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.
lo...@gmail.com <lo...@gmail.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
be...@google.com <be...@google.com>
be...@google.com <be...@google.com> #5
Any update on this? This has started to become a daily issue for my organization..
be...@google.com <be...@google.com> #6
I am also experiencing this issue, with the same use case, we also have a script that pulls data every morning. for the past months, it has been running great. and then it just started behaving weirdly.
During the different parts of the execution,
- deleting existing data
- creating new data
It is having issue with the Spreadsheet Service, with no helpful information.
During the different parts of the execution,
- deleting existing data
- creating new data
It is having issue with the Spreadsheet Service, with no helpful information.
be...@google.com <be...@google.com> #7
I am also experiencing the same issue.
My code:
line 1: function Racer(event)
line 2: {
line 3: var sheetName1 = "Applications: Account# Entry"; // labeling sheet names
line 4: var sheetName2 = "Applications: Credit Entry";
line 5: var sheetName3 = "Applications: Sage Entry";
line 6: var sheet = event.source.getActiveSheet()
line 7: console.log(sheet)
line 8:
line 9: //-----------------------------------------------------------------------------------------------------------------------------------
line 10: if (sheet.getName() == sheetName3) //if it is an edit in the correct sheet then
Sometimes my code will function without any problems. Other times without any changes it will get stuck on line 10 and not stop executing until I cancel the execution or my computer time for the day runs out.
The error message I am receiving via email:
Service Spreadsheets timed out while accessing document with id 1QDqGgQtAncVZS0zx2N7P7BA4-zakPB0k15P******. (line 10, file "Code")
A temporary solution that seemed to work for me:
copy and paste your code into a newcode.gs file
My code:
line 1: function Racer(event)
line 2: {
line 3: var sheetName1 = "Applications: Account# Entry"; // labeling sheet names
line 4: var sheetName2 = "Applications: Credit Entry";
line 5: var sheetName3 = "Applications: Sage Entry";
line 6: var sheet = event.source.getActiveSheet()
line 7: console.log(sheet)
line 8:
line 9: //-----------------------------------------------------------------------------------------------------------------------------------
line 10: if (sheet.getName() == sheetName3) //if it is an edit in the correct sheet then
Sometimes my code will function without any problems. Other times without any changes it will get stuck on line 10 and not stop executing until I cancel the execution or my computer time for the day runs out.
The error message I am receiving via email:
Service Spreadsheets timed out while accessing document with id 1QDqGgQtAncVZS0zx2N7P7BA4-zakPB0k15P******. (line 10, file "Code")
A temporary solution that seemed to work for me:
copy and paste your code into a new
ch...@google.com <ch...@google.com> #8
+ 1 i am seeing this consistently when running a script from a trigger which attempts to reformat a range.
Number of cells, normally no greater than 300k.
function formatTable(range) {
SpreadsheetApp
.getActiveSheet()
.autoResizeColumns(1, SpreadsheetApp.getActiveSheet().getLastColumn() )
.setActiveRange(range)
.setVerticalAlignment("top")
.setWrap(true)
.applyRowBanding(SpreadsheetApp.BandingTheme.CYAN) ;
};
Number of cells, normally no greater than 300k.
function formatTable(range) {
SpreadsheetApp
.getActiveSheet()
.autoResizeColumns(1, SpreadsheetApp.getActiveSheet().getLastColumn() )
.setActiveRange(range)
.setVerticalAlignment("top")
.setWrap(true)
.applyRowBanding(SpreadsheetApp.BandingTheme.CYAN) ;
};
lo...@gmail.com <lo...@gmail.com> #9
Also getting this, but I can narrow it down to one line.
I have tried different workarounds based on other responses.
This is a simplified script, basically, if I comment out setNumberFormat
and setNumberFormats
then it works, but no matter which one I use, the moment I use it I get the error.
Sep 14, 2020, 7:06:14 PM Error Service Spreadsheets failed while accessing document with id 1w-U7-Zh6bcY9_d0EARN8qes6k72zJy5Q2Nw-70tkYOM.
function onEdit_projections_UsageUnit(e) {
// the sheet that we are generating the dropdowns on
const range_check = (row, column) => (column === 2 && 1 <= row && row < 10);
if (!(
e.value != null
// value has changed
&& e.oldValue !== e.value
&& e.source.getSheetName() === SHEET_PROJECTIONS
&& range_check(e.range.getRow(), e.range.getColumn())
)) {
return;
}
Logger.info('onEdit_projections_UsageUnit activate');
// Option i
// const sheet = e.range.getSheet();
// Option ii
const sheet = e.source.getSheetByName(SHEET_PROJECTIONS);
// const sheet = SpreadsheetApp.getActiveSpreadsheet();
Logger.info(`onEdit_projections_UsageUnit sheet ${sheet.getSheetName()}`);
const mapRange = sheet.getRange('D3:9');
const mapColumns = mapRange.getNumColumns();
Logger.info(`onEdit_projections_UsageUnit mapRange ${mapRange.getNumRows()}:${mapColumns}`);
const modelRange = sheet.getRange('C3:C9'); //mapRange.offset(0, -1, mapRange.getNumRows(), 1);
const models = modelRange.getValues();
Logger.info(`onEdit_projections_UsageUnit models (${models.join(', ')})`);
for (const [index, [model, ]] of models.entries()) {
Logger.info(`onEdit_projections_UsageUnit each:${index} model:${model}`);
if (model === '') {
// wipe out formatting.
} else if (true) {
// option A:
//const rowRange = mapRange.offset(index, 0, 1, mapColumns);
// option B:
const rowRange = sheet.getRange(`D${3 + index + 1}:${3 + index + 1}`);
Logger.info(`onEdit_projections_UsageUnit each:${index} range:${rowRange.getA1Notation()}`);
// option 1:
//rowRange.setNumberFormat(`0.## blah`);
// option 2:
const sploosh = [new Array(mapColumns).fill(`0.## blah`)];
rowRange.setNumberFormats(sploosh);
Logger.info(sploosh);
}
}
Logger.info(`onEdit_projections_UsageUnit done done`);
}
Description
I have the sources of API 28 installed on my machine through the SDK manager. Looking at the sources is faster, although I lose formatting and contextual UI.
It seems it fetches the whole class documentation through network each time Quick documentation is triggered, which is a huge performance issue considering the documentation is already locally on my machine "thanks" to SDK manager. Also, that breaks offline usage or productivity on slow network (and my network isn't slow, we have fiber here, ~60Mbps symmetric per staff member).
This is a critical UX issue, I hope you raise it to maximum priority.
Android Studio 3.5 Canary 10
Build #AI-191.6183.62.35.5416148, built on March 28, 2019
JRE: 1.8.0_202-release-1483-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.4
Steps to Reproduce:
1. Ctrl + Q (or whatever the shortcut to "Quick documentation" is
2. Wait…
3. Was it quick?
4. Rinse and repeat: you get the daily experience of an Android developer who didn't learn the whole documentation by heart.