vercel__workflow/.changeset/lazy-resume-deployment-affinity.md at identify-condition-causing-reported-error

mirror of https://github.com/vercel/workflow.git synced 2026-09-14 19:59:43 +08:00

Files

T

Karthik Kalyan 439a495a71 fix(core): pre-check deployment affinity before the lazy resume write (#3374 )

The lazy hook fast path (#3345) hoisted the consumer's hook_received
write above the deployment-affinity guard (#2960), so a misrouted lazy
resume wrote its event before the guard could re-route the delivery.

Stamp the run's pinned deployment on the resume message
(hookInput.deploymentId, from the producer's resume context) and, on
the consumer, compare it against the ambient deployment id immediately
before the fast path: a match continues with no run fetch, a mismatch
fetches the authoritative run and hands it to the existing guard —
which keeps sole ownership of re-route/fail policy and remains the
authoritative protection before replay and step execution. The
re-routed message preserves the complete hookInput (it may hold the
only copy of the resume payload). Older messages without the field, and
worlds without deployment affinity, are unchanged: they skip the
pre-check and rely on the authoritative guard, the pre-guard write
staying convergent per (runId, resumeId).

Fixes the misrouted-lazy-resume unit test broken by the #2960/#3345
ordering: a modern misrouted resume now re-routes with zero event
writes, asserted for both hook_received and run_started.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-08-06 14:22:25 -07:00

183 B

Raw Permalink Blame History

@workflow/world, @workflow/core

@workflow/world	@workflow/core
minor	patch

Carry the run's pinned deployment on lazy resume messages so misrouted deliveries re-route before the hook_received write.

183 B Raw Permalink Blame History

183 B

Raw Permalink Blame History