"a.records is not iterable" airtable error

šŸž Report an issue
1

Hello there,

I have a issue with de scraper. I try to scrape Inoreader news section. It used to work fine but it seems that, when I try to scrape more than 5 news of the thread, iā€™m getting blocked. I get the following message: ā€œa.records is not iterableā€

I believe it comes from the infinite scroll option but Iā€™m not sure as it used to work fine before. Is it Inoreader that spotted my recurring scraping?

If anyone know what the ā€œa.records is not iterableā€ really means, it will be really helpful.

Cheers,

2

Hi @AdriBou,

Welcome to the community, and sorry you encountered a bug.

Are you trying to use a scraper with Airtable? We have seen such error message due to a bug in our Airtable integration that weā€™re working on.

3

Yes, thatā€™s correct. I use Airtable as database for scraping.

I conducted more thorough testing and realized that one article in Inoreader was causing this issue. However, I had encountered this error before that as well, so Iā€™m not 100% sure.

If itā€™s a bug caused by Airtable that you are currently addressing, then Iā€™m glad because it means this issue could be resolved soon.

Thank you for your response!

4

Can you share the error message like this?
Share the error

Also any automation link can be helpful for us to try to reproduce.

PS: this case is best for :lady_beetle: Report an issue

5

a.records is not iterable

{
  "clientErrorCode": "TypeError: a.records is not iterable",
  "trackError": "default",
  "clientErrorHistory": [
    {
      "clientErrorCode": "TypeError: a.records is not iterable",
      "message": "a.records is not iterable",
      "stack": "TypeError: a.records is not iterable\n    at kp (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/731.js:4:32373)\n    at zm.handle (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/731.js:4:50675)\n    at async chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/731.js:550:88358\n    at async wy.invokeFunction (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/731.js:550:88166)\n    at async wy.invokeSequence (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/731.js:550:79537)\n    at async wy.invokePlaybook (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/731.js:550:81036)\n    at async eg.execute (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/731.js:550:98709)\n    at async eg.executeWithResult (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/731.js:550:99264)",
      "fingerprint": [
        "{{ default }}"
      ]
    }
  ],
  "fingerprint": [
    "{{ default }}"
  ]
}
1 Like
7

Thanks, this is great input for us!

Weā€™ll check this issue and fix it. Stay on the radar via our :mega: Product Releases and by updating the app - we usually release on tuesdays (so you can update on wednesdays).