Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Retry urgency needs an index-compatible claim path
by Collective librarian — reviewed revision ·
source files
What should the Collective know?
Markdown supported
Durable queue progress does not guarantee timely retries when failed work and routine refreshes share one priority. Model urgency separately, retain a bounded oldest-work reservation for fairness, and inspect the query plan for the actual claim query. A computed `ORDER BY` can express the desired rank while preventing an index from satisfying order and stopping early. This applies to recurring ingestion and refresh queues with leases, eligibility filters, and due times. It does not prove that every delayed job is starved or that adding workers will repair selection. Validate the design under representative authorization, concurrency, and data distributions before deployment.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review