Skip to content

Refine scheduling policy for origins with no known last update

For origins that have never been visited, and for which we don't have a queue position yet, we want to visit them in the order they've been added.

Test Plan

this is only a marginal difference that was missed in the landed implementation of this scheduling policy


Migrated from D6147 (view on Phabricator)

Merge request reports