Upgrade StorageISBN lookup waits silently on WorldCat's Retry-After, then adds the item minutes later
Zotero 10.0.9, macOS 27.2. Add Item by Identifier with ISBN 9781003619260 (a new Routledge title that so far only WorldCat has).
According to the debug output, the WorldCat Turnstile check passes in the hidden browser within a few seconds. The search request that follows then gets HTTP 429 with Retry-After, and Zotero logs "Delaying 300 seconds for Retry-After". Nothing in the UI tells me that the lookup is waiting.
I started a second lookup about two minutes later. It got 429 as well, with Retry-After 186 s, and waited for those 186 s. It then succeeded and saved the item at 00:23:19.
So a lookup can sit for up to five minutes without any indication. It looks failed, but it still adds the item later. Earlier in the evening, this gave me duplicate copies after I had already added the book by DOI.
Two suggestions:
- Tell the user that WorldCat is rate-limiting and how long the wait is, or offer to cancel.
- Don't save an item from a lookup the user has already given up on.
Debug ID: D1714690772
According to the debug output, the WorldCat Turnstile check passes in the hidden browser within a few seconds. The search request that follows then gets HTTP 429 with Retry-After, and Zotero logs "Delaying 300 seconds for Retry-After". Nothing in the UI tells me that the lookup is waiting.
I started a second lookup about two minutes later. It got 429 as well, with Retry-After 186 s, and waited for those 186 s. It then succeeded and saved the item at 00:23:19.
So a lookup can sit for up to five minutes without any indication. It looks failed, but it still adds the item later. Earlier in the evening, this gave me duplicate copies after I had already added the book by DOI.
Two suggestions:
- Tell the user that WorldCat is rate-limiting and how long the wait is, or offer to cancel.
- Don't save an item from a lookup the user has already given up on.
Debug ID: D1714690772
-
dstillman Zotero TeamIn the Zotero 11 beta, add-by-identifier attempts that get 429s and don't succeed via another provider will just be skipped. We could potentially show a clearer status if any of the providers returned 429, though there's no guarantee that it's one that would have produced a result.