docs: sandbox behavior during lifecycle transitions#168
Open
Conversation
Explain what happens when users interact with a sandbox while lifecycle operations (pause, resume, connect, kill) are in progress. Add error reference table for lifecycle operations. Cross-reference from related pages.
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.
Summary
pause,connect,kill) to possible errors (NotFoundError,TimeoutError)Addresses the request from the thread: for every lifecycle method, document what happens when a user tries to use the sandbox while that operation is executing.
Note for reviewers
The error-to-operation mapping in the table is based on logical inference from SDK error types. Jakub should validate the exact mappings before merging.
Test plan
npx mintlify devand verify the new sections render correctly on the persistence page