Status Update
Comments
sm...@gmail.com <sm...@gmail.com> #2
ca...@gmail.com <ca...@gmail.com> #3
se...@google.com <se...@google.com> #4
Hi,
Did you get the popup on the cell where the formula goes asking to link the sheets and allow access?
Thank you.
ki...@gmail.com <ki...@gmail.com> #5
Did you get the popup on the cell where the formula goes asking to link the sheets and allow access?
I get it as usual, only the first time I try to import from non-public spreadsheet. Internal import error appears some time later.
se...@google.com <se...@google.com> #6
Can you share your use case? Do you use it from two different accounts or how you have it set-up?
ki...@gmail.com <ki...@gmail.com> #7
Can you share your use case?
I'm sorry, but I cannot do that. All my spreadsheets have confidential data in them. If I'll see again a test spreadsheet with the same issue I'll share it here.
Bu there is nothing fancy, just plain =QUERY(IMPORTRANGE(...), "WHERE Col1 IS NOT NULL",)
Do you use it from two different accounts or how you have it set-up?
Same problem is in different environments:
- both spreadsheets belong to a single account
- spreadsheets importing data from other spreadsheets - all in shared drive in workspace account
ki...@gmail.com <ki...@gmail.com> #8
a....@journeyagency.ru <a....@journeyagency.ru> #9
ki...@gmail.com <ki...@gmail.com> #10
Now I see in one of my spreadsheets that this
IFERROR(IMPORTRANGE("id", "A:A"), IMPORTRANGE("id", "A:a"))
does not shield you completely from that issue. It might still occur :(
d....@gmail.com <d....@gmail.com> #11
ki...@gmail.com <ki...@gmail.com> #12
os...@gmail.com <os...@gmail.com> #13
so...@gmail.com <so...@gmail.com> #14
73...@gmail.com <73...@gmail.com> #15
er...@gmail.com <er...@gmail.com> #17
ms...@costco.com <ms...@costco.com> #18
rx...@gmail.com <rx...@gmail.com> #19
ki...@gmail.com <ki...@gmail.com> #20
Now I also have an issue with a few tables with manually giving permissions for IMPORTRANGE
.
- I get
#REF
error. - Blue button is displayed, so
/canaddimportrangepermissions
successfully returns, which means I do have enough permissions for both spreadsheet (which is true). - I click the blue button and get the warning, permissions were not added -
/addimportrangepermissions
returnedsuccess: false
.
This behavior is persistent, started about 12 hours ago.
This might be connected to the original issue as on of my colleagues said that not only letter-case change temporarily solves the issue, but also adding permissions again through /addimportrangepermissions
.
These spreadsheets are not public, but if you need ids to check some logs:
- id:
1eqS_7SEO3kQBFm393LU0TSc7kZnAH9WNzGvYeS_7XFw
- donorId:
1nnIs3GDKni47ei9fuCdmDIQqOFU9fxsUSo53ZktMTsE
09...@gmail.com <09...@gmail.com> #21
su...@gmail.com <su...@gmail.com> #22
er...@gmail.com <er...@gmail.com> #23
ki...@gmail.com <ki...@gmail.com> #24
I think it is global, but canaddimportrangepermissions
is Can Add IMPORTRANGE Permissions
. :)
fu...@gmail.com <fu...@gmail.com> #25
se...@google.com <se...@google.com> #26
Hello,
I have forwarded this issue internally.
Regards.
tp...@igm.technology <tp...@igm.technology> #27
[Deleted User] <[Deleted User]> #28
me...@djis.edu.sa <me...@djis.edu.sa> #29
jo...@truaxnw.com <jo...@truaxnw.com> #30
I've literally built our business's infrastructure around importrange and I'm sure there are many many others who've done the same.
tm...@themotorcyclecompany.com <tm...@themotorcyclecompany.com> #31
mb...@gmail.com <mb...@gmail.com> #32
I had it both on new import range's before allowing access to the IMPORTRANGE , and on old ones which worked just fine for the last year and suddenly started making problems
This is really annoying as all my calculations and all my data get messed up when this happens and I cant work on them till the error goes away
se...@google.com Please help us ASAP Thanks so much
bj...@valorcollegiate.org <bj...@valorcollegiate.org> #33
ma...@gmail.com <ma...@gmail.com> #34
[Deleted User] <[Deleted User]> #35
me...@djis.edu.sa <me...@djis.edu.sa> #36
at...@gmail.com <at...@gmail.com> #37
ma...@planetcellinc.com <ma...@planetcellinc.com> #38
No Pattern When it shows #REF - Import Range Internal Error
No Time or any reason to understand
Have tried all "Remedies" suggested by people use iferror/iserror/change user/use ranges in CAPs without CAPs...
Hopefully Google Team to find once for all solution to this problem!
kw...@wvusd.org <kw...@wvusd.org> #40
mr...@gmail.com <mr...@gmail.com> #41
pf...@rosstech.ca <pf...@rosstech.ca> #42
100+ tabs, 30+ sheets.
we run our CRM / ERP on the sheets.
our work around is to go to the offending tab, ctrla, ctrlx, then ctrlz.
seems to fix it everytime, but what a nightmare.
my fingers are cramped.
happy to share our most frequently occurring sheet if that helps.
cu...@affectrix.org <cu...@affectrix.org> #43
=IFERROR(QUERY(ImportRange("sheet ID", "tab name!A3:v1500"), "Select * where Col1 is not null",1),
IFERROR(QUERY(ImportRange("sheet ID", "tab name!A3:V1500"), "Select * where Col1 is not null",1),
IFERROR(QUERY(ImportRange("sheet ID", "tab name!A3:v1500"), "Select * where Col1 is not null",1),
IFERROR(QUERY(ImportRange("sheet ID", "tab name!A3:V1500"), "Select * where Col1 is not null",1)))))
Notice the lower case v's. Works for me, but maybe I'm just lucky !
ma...@planetcellinc.com <ma...@planetcellinc.com> #44
IFERROR(IMPORTRANGE("id", "A1:B20"),iferror(IMPORTRANGE("id", "A1:b20"),iferror(IMPORTRANGE("id", "a1:B20"),IMPORTRANGE("id", "a1:b20"))))
Means, Recall same fuctions 4x times using CAPS/Non CAPS in Range names.
cu...@affectrix.org <cu...@affectrix.org> #45
ad...@arcosabroad.com <ad...@arcosabroad.com> #46
ma...@telusinternational.com <ma...@telusinternational.com> #47
er...@gmail.com <er...@gmail.com> #48
Last this we got was:
"se...@google.com <se...@google.com> #26Oct 29, 2021 11:43AM
11:43AM
Hello,
I have forwarded this issue internally.
Regards.
"
so...@mail.ru <so...@mail.ru> #49
re...@gmail.com <re...@gmail.com> #50
sa...@plugable.com <sa...@plugable.com> #51
sa...@plugable.com <sa...@plugable.com> #52
This issue is also occurring across our entire workspace. Our organization makes heavy use of IMPORTRANGE
for various business sheets. The issue itself seems to be per-session, not per-sheet. For instance, one user can be viewing the spreadsheet without issue, while another sees the reference error associated with the failed IMPORTRANGE
.
Sheets API calls are also affected in the same way. Occurrence is intermittent/unpredictable.
sa...@plugable.com <sa...@plugable.com> #54
Can you elaborate more on what the root cause of this issue was? Our organization depends on this functionality, and if the issue occurs again, we'd like to have more information to work with.
sa...@plugable.com <sa...@plugable.com> #55
This issue has not been resolved. We're still seeing the same "Import Range internal error." on sheets.
er...@gmail.com <er...@gmail.com> #56
I have files that are Importing Range form monthly dumps, generating individual Staff, Client and Department reports on expected and actual billing details.
Because of this issue, I have set a cell with a if error = "there are issues" and a Dashboard looking up to all these reports.
So I have Dashboard (importrange cell a1...) Reports (several importranges to several...) Dump.
When I open the Dashboard and I go from 0 errors to 23 files with errors. Sometimes I open the report and all Importranges recycle and I have no error. But sometimes, I have to delete and Ctrl+z the importrange cells so it recycles.
Please note that, lucky me, I started building this during this whole importrange situation. SO I don know if having the "Dashboard (importrange cell a1...) Reports (several importranges to several...) Dump" is forcing the error, or if we still indeed have issues (even though Goggle said it's fixed).
If anyone could comment and share some thought/expertise, I appreciate it.
sa...@plugable.com <sa...@plugable.com> #57
This is definitely a Google server-side issue. No patch we can make client-side will eliminate this. I suspect this "fix" is implemented but not pushed live yet ("In Prod" flag in the sidebar is false). Hopefully someone at Google can comment here and let us know the status of this critical issue.
ad...@aihti.com <ad...@aihti.com> #58
er...@gmail.com <er...@gmail.com> #59
ad...@aihti.com <ad...@aihti.com> #60
ni...@gmail.com <ni...@gmail.com> #61
uk...@gmail.com <uk...@gmail.com> #62
mb...@gmail.com <mb...@gmail.com> #63
But doesn't happen so often or for so long
Google Please fix it completely
ca...@gmail.com <ca...@gmail.com> #64
tm...@themotorcyclecompany.com <tm...@themotorcyclecompany.com> #65
ay...@noon.com <ay...@noon.com> #66
[Deleted User] <[Deleted User]> #67
ca...@gmail.com <ca...@gmail.com> #68
ca...@gmail.com <ca...@gmail.com> #69
"Status
Fixed"
We need to open other case
lo...@google.com <lo...@google.com>
dr...@gmail.com <dr...@gmail.com> #71
ja...@google.com <ja...@google.com>
lo...@google.com <lo...@google.com> #72
It has been reported that this issue is still present
fi...@gmail.com <fi...@gmail.com> #73
Please make it work and high priority for fixing!
[Deleted User] <[Deleted User]> #74
er...@gmail.com <er...@gmail.com> #75
lo...@google.com <lo...@google.com> #76
Hello.
Unfortunately, this error is due to very different circumstances. As we cannot access any private information from Issue Tracker, we cannot analyze these cases from here.
The best option for users who are experiencing this behavior is to open a new
Have a nice day!
Description
A short description of the issue:
For more than 10 days already people report frequent cases of getting error "Import Range internal error" while using
IMPORTRANGE()
function where it previously worked fine.What steps will reproduce the problem?
Not sure how to reproduce. I've seen this behavior within quite heavy spreadsheets as well as within newly created ones containing just a few cells of data.
What is the expected output? What do you see instead? If you see error messages, please provide them.
Data should be imported as usual, but often it is replaced with the error message "Import Range internal error".
Please provide any additional information below.
There is a SO question on the matter:https://stackoverflow.com/q/69593421/279806
Only dirty workarounds are known now.
One would be to change case of any letter in the second argument (range being imported) of
IMPORTRANGE()
.Another one is to repeat
IMPORTRANGE()
one original and another with some letter-case changes) inIFERROR()
like so: