Open MoralCode opened 3 years ago
From looking at the minified code around the place where it says the error is, it seems like this issue is being caused by this Async call: https://github.com/GV14982/async-airtable/blob/d9b517f67349f0dceb41f56846e52dc06ea7e1cb/src/asyncAirtable.ts#L264-L276
Edit: the sourcemap seems to suggest its actually this catch block that's throwing the error : https://github.com/GV14982/async-airtable/blob/d9b517f67349f0dceb41f56846e52dc06ea7e1cb/src/asyncAirtable.ts#L184-L186
i suspect this happens in cases where there are multiple pages of records to fetch and the Airtable server goes down or something in the middle of that interaction
Thanks for all your work on this!
Yeah feel free to submit a PR. If you opt not to I will take a look at it as soon as I have some more time!
I've been seeing quite a few instances of the following error in the monitoring software we use for vacfind:
I'm working on getting the included sourcemaps to process correctly, but this seems to me to be a relatively straightforward case of an
UnhandledPromiseRejection
.Searching online leads me to this issue that mentions this error message and refers to the Airtable API docs which state that:
I have not personally found a way to reproduce this issue since the docs seem to say that it only happens in cases of timeouts or the airtable server going down. Although airtable seems to briefly (<30 sec) go down somewhat frequently, this isn't something that I am able to reproduce intentionally.
Would you accept a PR to add in a handler to catch these 422 LIST_RECORDS_ITERATOR_NOT_AVAILABLE errors, and If so, how would you prefer to have AsyncAirtable handle it?