vercel__workflow/.changeset/fail-cross-deployment-runs.md at quickjs-vm-default

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

Files

T

Alex Langenfeld 79e4c04409 fix(core): re-route runs delivered to the wrong deployment (#2960 )

## Summary & Motivation

A queue callback that reaches a deployment other than the one its run is pinned to derives the per-run encryption key from the wrong master key, so the delivery fails before user code runs and the run dies as a blank "exceeded max retries". The delivery is re-enqueued explicitly addressed to the run's own deployment — strictly better-targeted than the send that misrouted — and the run is failed with the new `DEPLOYMENT_MISMATCH` error code only once `WORKFLOW_DEPLOYMENT_MISMATCH_MAX_RETRIES` (default 3) is spent. Gated on the new World capability `deploymentAffinity`, so worlds with synthetic or version-tagged deployment ids are unaffected.

## Test Plan

Unit tests added for the guard and both runtime paths; local vitest and typechecks pass.

2026-08-05 14:57:37 -05:00

376 B

Raw Permalink Blame History

@workflow/core, @workflow/errors, @workflow/world, @workflow/world-vercel

@workflow/core	@workflow/errors	@workflow/world	@workflow/world-vercel
patch	minor	minor	patch

Re-route a queue delivery that reaches a deployment other than the one its run is pinned to, retry transient publishing failures through normal queue redelivery, and fail the run with the new DEPLOYMENT_MISMATCH error code once the recovery budget is spent.

376 B Raw Permalink Blame History

376 B

Raw Permalink Blame History