Merged
Conversation
dan-woz
approved these changes
Jun 20, 2025
Collaborator
dan-woz
left a comment
dan-woz
left a comment
There was a problem hiding this comment.
Looks good! Might be possible to tighten up the ref typing a bit, but I assume it's basically not worth the effort.
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.
To completely eliminate the issue of large workflows being stored in your message queue, you can now provide a custom callback storage backend to the
WorkflowMiddleware. A callback storage backend is responsible for storing and retrieving the list of callbacks. For example, you could implement a storage backend that stores the callbacks in S3 and only stores a reference to the S3 object in the message options.