You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(run-store): fall back to legacy on an idempotency-key reset when the new DB matches nothing
Routing a predicate reset to the new database ONLY broke resets during the rollout window: a key
minted before an org flipped still lives on a legacy-resident run (idempotency TTL up to 30 days),
so a new-only reset matched zero rows, returned 404, and left the stale key deduping child triggers.
The reset now checks the new database first and falls back to legacy when nothing matched, so it
clears the key wherever the run lives; a fully-drained env still never touches legacy.
0 commit comments