fix(sessions): persist workers before provider identity assignment - #531
Merged
Merged
Conversation
Keep Clay record filenames stable before and after provider identity assignment. Preserve durable history, legacy records, and failed-worker creation rollback.
Contributor
|
This issue has been resolved in version 4.3.0-beta.7 (main). To update, run: -- Clay Deploy Bot Build anything, with anyone, in one place. |
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
1 participant
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.
Fresh Split Workers have no provider session ID until their provider starts. Saving them previously returned false, preventing a second Worker from being created.
Persist Clay session records under a stable internal identity and keep provider identity as metadata. Provider adoption preserves the original history/file; legacy records and failed-creation cleanup remain compatible. Durable appends still fail closed if no record exists.
Validation: independent
npm testpassed (2,444 passed, 1 skipped, 0 failed). Production manager/factory regressions cover provider-less creation, real SDK identity adoption, reload, durable recording, and rollback. Live second-Worker creation awaits deployment; no daemon was restarted.