kami
802d5961ac
The worker took the oldest pending facts by id and attempted them. Once the oldest batch entered backoff the worker kept selecting the same rows, found none of them due, and did nothing. One unresolvable fact at the head of the queue froze enrichment for every fact behind it, up to the hour-long backoff cap, forever. The worker now scans up to a thousand pending rows and attempts the first batch that is actually due. Retry state for rows that left the queue is forgotten, a failed store write backs off the same way a failed resolve does, and the status counts pending, backed off and exhausted over the rows it saw. Found in review of #83.