Fix: Resolve video preview conflict by updating node ID#316
Merged
Conversation
…leCloudPlatform/accelerated-platforms into aburhan-update-VeoVideoSave
arueth
approved these changes
Oct 27, 2025
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
3 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.
Problem: The VeoVideoSaveAndPreview node was using the same "id" in multiple workflows. Since this node's JavaScript uses its id as a key to persist video data in localStorage, loading one workflow would incorrectly display the cached video from another.
Solution: Changed the conflicting node id. This breaks the localStorage key collision, ensuring each preview node only loads its own vi