Files
Duriin-API/workers
ImBenjiandClaude Opus 5 cbf1e6cafd fix: the outcome worker was starving its own queue
Separate bug from the cache, same symptom. The candidate query approximated
maturity with '+horizon_days days', which is looser than the truth because 20
trading days is 28 calendar days. So the oldest hundred open rows were almost all
horizon-30s that were not due yet, 98 of them, and those slots do not free up for
weeks. Measured just now: 54 live predictions genuinely ready to score, zero of
them inside the window. The worker sat there logging nothing at all.

It only looked like it was working before because the three rows it could see were
being retired as unresolvable every poll, which freed the slots. Fixing the cache
stopped the retiring and revealed the stall underneath.

1.5x + 2 calendar days overshoots a trading day span at every horizon in use, so
the limit now gets spent on rows that can plausibly be scored. The js trading day
filter is still what decides.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-10-09 14:21:17 +01:00
..