When a job board fails
One source failing does not fail the search. The others still answer, and the failure is recorded rather than hidden.
Boards rate-limit, go down, and occasionally change their API without warning. One failing source does not fail the search: the others still answer, and you get what they returned.
- The failure is recorded rather than swallowed, so we can see which source is having a bad week instead of quietly serving you less.
- A board that keeps failing is skipped for a while rather than slowing every search down while it is broken.
- A board that serves one country and refuses another is normal and by design, not a fault.
If a search looks thinner than you expected, running it again a few minutes later is genuinely worth doing.
Where it stops
There is no public status page and no per-board indicator in the results. The progress bar counts searches, not boards, so if a source is down the only sign you will see is that the search returns less.
Related articles
- Why some searches take longerAnything already in the index is instant. A search nobody has run recently has to ask the boards live, and the slowest one sets the pace.
- Where results come fromJob boards and national employment services, other public job sites, and openings pulled straight from companies' own careers pages.
- When a search returns nothingEither your filters removed everything, in which case the page names the one responsible, or the index holds nothing yet for that query.
Did this answer your question?
Still stuck? Ask us directly, and mention this article so we know where to start.