[feat] Add flow retry capability with state preservation #254
+439
−54
Conversation
This file contains 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
Reorganize button implementation and update visual design: - Move inline button component from header to dedicated file - Update button styles with rounded corners and consistent height - Adjust shadow and typography properties for better aesthetics This change maintains functionality while improving design consistency across the playground interface.
Create execution snapshots that capture full graph context during execution: - Add ExecutionSnapshot type to store complete execution state - Include nodes, connections and flow data alongside execution details - Modify putExecutionAction to store entire snapshot instead of just execution - Add helper function to create snapshots from current graph state This change enables proper replay and debugging of past executions by preserving the complete graph state at execution time.
Add ability to retry failed flow executions with the following features: - Preserve completed step results from original execution - Retry only failed steps while maintaining execution context - Add retry button in failed step UI - Support full graph state restoration from execution snapshots This change allows users to retry failed flows without recreating the entire execution, saving time and maintaining execution history. Failed steps can be retried while preserving successful results from previous attempts.
Clean up execution state management and snapshot handling: - Restructure createExecutionSnapshot to use object params for clarity - Fix step completion check to preserve completed step results - Ensure retry uses original graph state from snapshot - Remove unnecessary status filtering in executeJob This change improves code maintainability and fixes issues with execution state preservation during retries.
|
@toyamarinyon is attempting to deploy a commit to the Edge Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dec18b_output.mp4I was able to record a stream of Overloaded errors in the Preview environment, which were resolved by re-running. |
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.
Screen.Recording.2024-12-18.at.17.59.19.mov
Changes
Testing
Note
It is difficult to artificially cause an error and then succeed with a further retry, so it is OK if the normal case can be confirmed.
Execute a node on the playground
/p/:agentIdExecute a flow on the playground
/p/:agentId