Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bug: Unable to parse range
See original GitHub issueFacing issues when grabbing data when using other sheet’s besides the test sheet.
Unable to parse range.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Google spreadsheet API, 400 error bad request : unable to ...
Error: Unable to parse range: Emmet!A2:C12. I had to manually create the sheet named Emmett in the spreadsheet and then it worked like...
Read more >Google Sheet 400 Error - Unable to parse range
ERROR: 400 - {"error":{"code":400,"message":"Unable to parse range: A:D1:undefined1","status":"INVALID_ARGUMENT"}} StatusCodeError: 400 ...
Read more >Unable to parse range: 'manufacturing_log'!1:1 · Issue #15108 ...
Sentry Issue: APPSMITH-2ZG AppsmithPluginException: Unable to parse range: 'manufacturing_log'!1:1 at com.external.plugins.
Read more >Trouble connecting Google Sheets and Clickfunnel "Unable to ...
With that “Unable to parse range: 'Contact List'!A:A” error, it usually indicates that the spreadsheet/worksheet was renamed since it was ...
Read more >Error cloning app: Unable to parse range
Account 1,199 · App Management 1,222 · Automation 8,048 · Bug 11 · Data 7,102 · Errors 4,265 · Expressions 8,699 · Integrations...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you! I’d add this to documentation obviously for other users (assuming you’re on it already😉)
And no sorry needed at all! Thank you again!
Ah! The last part of the URL should be the name of the tab, which in your case is “Form Responses 1”. Here’s the correct URL to use: https://opensheet.elk.sh/1GpUteMOS41K7c3pj7b77xF4F-7PTKZyfPK4FVQr8SVc/Form+Responses+1
Sorry about that! The error message is a bit cryptic.