I also just received this error for the first time today, on a ~100 page doc with ~100 references. I tried all the steps in the troubleshooting section, including making a copy of the doc and bisection-searching the references - it kept happening seemingly regardless of which references I deleted (I deleted all but one more than once, with different ones remaining, e.g. by starting by deleting early sections first, then on a second run by deleting later sections first).

My doc has 3 Gdoc Tabs, and if I delete both of the second and third tab, the error disappears. But not if I only delete the contents of the tabs and leave the tabs there.

Through repeated bisection searching in a copied document, I did find one reference that, if I deleted it, the error disappeared. But when I deleted that one in my original doc, I still got the error. Which MAYBE points to there being more than one broken reference.

Last week I turned up the blocking settings on noscript, and I wonder if that might have caused the breakage? I've since re-allowed all the google related domains.

I have this javascript error in my connector prefs:

[JavaScript Error: "400: Google Docs request failed.

{
"error": {
"code": 400,
"message": "Invalid requests[0].deleteNamedRange: No named range with ID: kix.a8imd4xj080v",
"status": "INVALID_ARGUMENT"
}
}

batchUpdateDocument@moz-extension://01062f54-2116-420d-8ea6-2d6e0cf35c2f/zotero-google-docs-integration/api.js:365:11
" {file: "[object Object]"}]

[JavaScript Error: "400: Google Docs request failed.

{
"error": {
"code": 400,
"message": "Invalid requests[0].deleteNamedRange: No named range with ID: kix.a8imd4xj080v",
"status": "INVALID_ARGUMENT"
}
}

batchUpdateDocument@moz-extension://01062f54-2116-420d-8ea6-2d6e0cf35c2f/zotero-google-docs-integration/api.js:365:11
" {file: "[object Object]"}]

....

(there are many of these, most with different kix.XXXX ids.)

Sorry, there's currently a bug in the Google Docs integration handling of tabbed documents. We'll release a fix as soon as possible. You can work around that in the meantime by only citing in the first tab, or copying the contents of the tabs with citations into new documents. We'll update this thread once a fix is out.

I see there was an update today, and this issue seems to be resolved now. Thank you Adomas!