Skip to content
Discussion options

You must be logged in to vote

Good catch. You were right on both counts: the missing and cutoff passes always started from page 1, and with the 5-page-per-pass cap, items further down the list were never reached once the first pages were all on cooldown.

This is fixed in #294. Each pass now remembers which API page it stopped at and starts from there on the next cycle. When it pages past the end of available data, it wraps back to page 1 within the same cycle so nothing is permanently skipped.

The upgrade pass already had offset-based rotation for this reason. The missing and cutoff passes just lacked the same treatment. The fix also ensures that when the batch fills partway through a page, the offset stays on that pa…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by av1155
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants