Repository navigation
fix(workflows): save overlapping join history in order - #24
Merged
Merged
Conversation
This was referenced Nov 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #20.
Overlapping
ctx.joinbranches could save history thatloadStoragecannot read, so replay failed withName index N not found in registry. On actors, overlapping saves also failed withState cannot be mutated by another action while an experimental state-aware database transaction is active. Each failure counted as a step failure, so finished steps ran again and large joins ran out of retries.flush()runs one save at a time per workflow, so an older snapshot cannot land after a newer one.executeStepmarks step metadata dirty when a step finishes or fails, so a sibling's earlier save cannot leave it asrunning.examples/docs/onboarding/index.tssoformat:checkpasses, and removes the danglingdocs/AGENTS.mdsymlink (its target was removed inbaba281).rivetkit3.0.4mainSame fix in engine-ee: rivet-dev/engine-ee#1776.
This is part 1 of 5 in a stack: