Hi, We've been hit by "Loading..." issue again. The spreadsheets that are cursed with the issue remain in that state for significant time (for up to an hour). Anything depending on correct calculation in that spreadsheets breaks :(
It look like there is issue while ImportRange() and the response with error gets memcached and bound to spreadsheet cells the range should be loaded into. And only necessity to free the memcached memory for other systems makes spreadsheets work again. I imagine that with addition of extra datacenter to Google Infrastructure the issue will persist much longer. Can anybody at Google shed any light on the topic? Regards, m. On Wed, Jun 17, 2009 at 22:42, Myroslav Opyr <myros...@quintagroup.com>wrote: > Hi, > > We've faced a couple of issues with Spreadsheets API. We have developed > "Spreadsheet Creation Procedure" that create spreadsheet with CellsFeed (in > Batches) that contains =ImportRange(...) functions. The spreadsheets created > in that way are sometimes "corrupted" in two similar but different ways. > > The first and more "difficult" to cope with is "Loading..." one. > Unfortunately the issue is not easily reproducible. It is statistically > reproducible in 1 case per 15-20 attempts. > > The ImportRange(...) function in that rare cases refuses to load external > range. When opened in Google Spreadsheets GUI (i.e. via web), the cell that > contains the function says "Loading..." in gray font and refuses to load the > range. Attempts to change that function parameters, reloading the > spreadsheet in GUI, doesn't help. More then that, if spreadsheet contains > multiple ImportRange functions, neither of them works. All seem to get > "stuck" in "Loading..." state. We call such spreadsheet "cursed". Formulas > are perfectly correct, because the "broken" ImportRange formulas copied out > to brand new spreadsheet work properly. Usually such spreadsheet stays > "cursed" for at least several hours, today we've had similar spreadsheet to > resurrect itself in less then hour after opening in GUI (the spreadsheet was > created 12+ hours in advance and accessed via API only within that > 12+hours). Unfortunately I have little understanding, why that happens, > except for explanation that "Range Importer" process assigned to the > spreadsheet hangs until restarted at Google. > > > The other case, a bit "simpler" (but not less annoying) is "#REF" one. This > one happen almost every time we perform our "Spreadsheet Creation > Procedure". > > The issue means that ImportRange function renders as "#REF" error. The > issue can be corrected either by > > - opening Spreadsheet in GUI (via web) changing second parameter of > ImportRange(...), i.e. changing the range to be different (doesn't matter > bigger or smaller). Note, changing it back to original parameter returns > "#REF" error. > - or opening Spreadsheet in GUI and closing it. Opening Spreadsheet in > some time (usually 15min-3hours) resolves the issue. Note noting is being > edited in the spreadsheet itself, "pushing" the process with Opening in GUI > is enough. > > > You can notice that I'm mentioning "opening in GUI" as separate step, as > the software usually works via Spreadsheets API, manipulating Spreadsheets, > and pulling results of computation out of them. Thus "opening in GUI" is > manual process we are forced to do manually if some spreadsheets doesn't > work properly. > > We've submitted bug report via request.py (with less details, as we had > less statistical data then) more then week ago, but never heard back about > it yet. Asking in the Group to find if anyone has more experience with it. > > FYI, we are using python libraries (and API v1.0 consequently). > > > Regards, > > m. > > P.S. Sorry for "many letters" but less would hardly give more info. > -- ..................................................................................................... Myroslav Opyr ▪ CTO ▪ Quintagroup ▪ http://quintagroup.com ˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Docs Data APIs" group. To post to this group, send email to Google-Docs-Data-APIs@googlegroups.com To unsubscribe from this group, send email to google-docs-data-apis+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Docs-Data-APIs?hl=en -~----------~----~----~----~------~----~------~--~---
