Workable rate-limited us before the first board
On 18 November 2026 the refresh's first request to Workable was answered HTTP 429 (too many requests) with Retry-After 84,362 seconds: the host asked us to wait about 23 hours. The lane stops at the first such answer, so none of the 10,785 Workable candidates was read and the listing does not name Workable. Reading it from another address would get past the limit; we count that as evasion and do not do it. On 19 November Workable answered 3,834 requests at one a second, then sent a 429 with Retry-After 86,400 seconds. The 6,951 boards still unread wait for a later refresh.
One gap, found while writing this page. An earlier attempt at the 19 November refresh, which did not finish, began about three and a half hours before that 23-hour wait had run out; Workable answered 3,840 requests before its lane stopped (the log does not say why). The pass reported here began 81 minutes after that stop. The refresh honours Retry-After within a run but does not carry it from one run to the next, so neither run knew of the earlier wait. The fix is to keep each host's wait between runs.
Fixed on 20 November 2026. Both 19 November runs were cut off after about 3,840 requests at one a second, so we now treat Workable's limit as a daily request count, not only a rate. The refresh now keeps each host's Retry-After between runs and holds Workable to 30 requests a minute and at most 1,800 requests in any 20 hours, so its boards are read on a six-day cycle, never-read boards first. The 20 November refresh read 1,800 Workable boards, and none of its eight lanes received an HTTP 429.
Personio pushed back at four at a time
On 18 November 2026, after 515 answers, 20 of the lane's last 50 were 403 or 429, and the lane stopped itself as designed. The rerun the same day, one request at a time and at most one a second, checked the remaining 6,682 boards in 2.8 hours with 0 failures. Personio has run at that pace since.
We removed a whole system for its terms
The first refresh, on 18 November 2026, included BambooHR: 10,187 boards holding 51,717 jobs. Its developer terms bar crawling its interfaces or content without written consent, and no documented public feed stands behind its careers pages. It was taken out of the index, the refresh and the search options. SmartRecruiters was never added: its feed's robots.txt allows only LinkedIn's crawler.
A few big boards crowded out everyone else
The first test search returned 500 jobs from only 21 companies, because a few large boards held hundreds of matching sales roles. We added a cap per company. With a cap of five, the test search returned 500 jobs from 135 companies.
A slow board was overtaken and dropped
Results were kept in the order the boards finished. A large Lever board, read at one request a second, could finish last and be cut off when the 500th job arrived: one test run had 0 Lever jobs although Lever held newer matches. Jobs now come out in the order of each board's newest match, and the next run had 17 Lever jobs.
Descriptions in the wrong language, and a dead link domain
Personio's feed carries descriptions in the account's main language only, so a job published only in English came back empty: 0 of 6 on one test board. The reader now asks for English when a description is missing: 6 of 6. A Recruitee job link pointed at a company's own careers domain, which no longer resolved; links now use the recruitee.com address, which still answered.