MS: Persistent Instance Artefacts#757
Merged
Merged
Conversation
…es that were uploaded by workers during an processes' execution)
…s in user tasks are cached in the MS to ensure that they are accessible even if the engine is not reachable or if the user task data is lost on the engine
…Labs/proceed into persistent-instance-artefacts
…Labs/proceed into persistent-instance-artefacts
…t-instance-artefacts
…t-instance-artefacts
|
✅ Successfully created Preview Deployment. |
canptura
reviewed
Jun 12, 2026
canptura
approved these changes
Jun 12, 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
2 participants
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
Artefacts files for instances are stored in the MS so they can be accessed when the engine is not reachable. Artefacts might be files that are uploaded by a user while they are working on a user task.
Details