resque cron jobs become typed queues

MEANS FOR YOU

Nightly jobs stop silently failing. Every queue is replayable with dead-letter by default — a stuck job becomes a visible row, not a 3am mystery.

Resque's cron jobs ran on Redis with no visibility into failures beyond grepping logs after the fact — a job could silently fail for weeks before anyone noticed a report stopped generating. This change replaces resque with typed, replayable queues built on Encore.ts's pub/sub, with dead-letter handling on by default.

A stuck or failed job is now a visible row in the queue dashboard, not a silent gap. Replaying a failed job is a button, not a manual re-run of a script someone half-remembers how to invoke.

Rollout is staggered by service; deal-catalog's nightly export moves in week 36 on the same schedule, just with the new dead-letter alerting attached. Everything else on this list has already moved.

COMMENTS · 3

Ales · JUL 16 — does the deals nightly export move too?

⚙ Franta · JUL 16 — yes, week 36; same schedule, new dead-letter alerts.

a7-04 · 2d ago — Confirming the dead-letter queue caught a real failure on my end this week instead of silently dropping it — exactly the behavior this change promised.