[GH-ISSUE #136] feature req: honor 429 Too Many Requests properly #81

New issue

Open

opened 2026-10-18 21:14:10 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-18 21:14:10 +00:00

Owner

Originally created by @Zocker1999NET on GitHub (Sep 30, 2026).
Original GitHub issue: https://github.com/open-webui/oikb/issues/136

context

I pointed oikb against a Bookstack wiki instance I have admin access to. After some amounts of requests, oikb received 429 Too Many Requests from our Bookworm instance.

actual

oikb skipped the errored document & just continued making more requests

expected

oikb honors 429 by waiting the given time in the Retry-After header until to repeat this request (& also does not continue with further requests).

reasoning

While I should be able to increase the rate limiting, I do not want that. Because most probably that setting is global only & so I cannot differentiate oikb from other "normal" users. Also I do not want my oikb experiments to make the experience for other users worse. And the rate-limiting applied by Bookstack does ensure that.

Also, I'm not interested in oikb finishing as fast as possible. I'm just interested in that it will complete, successfully, in a reasonable amount of time for the content it attempted to sync.

Further, supporting 429 in general would just further help with running oikb against services user do not have admin control over.

Originally created by @Zocker1999NET on GitHub (Sep 30, 2026). Original GitHub issue: https://github.com/open-webui/oikb/issues/136 ## context I pointed oikb against a Bookstack wiki instance I have admin access to. After some amounts of requests, oikb received `429 Too Many Requests` from our Bookworm instance. ## actual oikb skipped the errored document & just continued making more requests ## expected oikb honors 429 by waiting the given time in the `Retry-After` header until to repeat this request (& also does not continue with further requests). ## reasoning While I should be able to increase the rate limiting, I do not want that. Because most probably that setting is global only & so I cannot differentiate oikb from other "normal" users. Also I do not want my oikb experiments to make the experience for other users worse. And the rate-limiting applied by Bookstack does ensure that. Also, I'm not interested in oikb finishing as fast as possible. I'm just interested in that it will complete, successfully, in a reasonable amount of time for the content it attempted to sync. Further, supporting 429 in general would just further help with running oikb against services user do not have admin control over.

bsakaguchi commented

2026-10-18 21:14:10 +00:00

Author

Owner

@FirstSanny commented on GitHub (Oct 5, 2026):

Currently have the same problem with our confluence instance. Proper handling would be awesome.

@FirstSanny commented on GitHub (Oct 5, 2026): Currently have the same problem with our confluence instance. Proper handling would be awesome.

bsakaguchi referenced this issue

2026-10-18 21:14:22 +00:00

[PR #81] [CLOSED] fix(history): give each thread its own SQLite connection (fixes #39) #103