[24.0] Fix workflow run form failing on certain histories #17869
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.
If we don't replace connected values with concrete value in the run form we won't run into errors when trying to use datasets in the history as potential inputs to input parameters that are already connected. This doesn't seem necessary, and makes the run form behave more like workflow scheduling. Should fix various 500 errors that are possible if there are failed or otherwise unexpected datasets in a history.
Fixes https://sentry.galaxyproject.org/share/issue/b162b010af894eecafdaea3ae1fd8e19/:
How to test the changes?
(Select all options that apply)
License