fix(core/pipeline): exclude correlation IDs (and more) when re-running #7374
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.
We recently added the ability to re-run active executions (#7293). Turns out there are some junk fields in execution triggers that have historically been fine to accidentally include when manually triggering (e.g.
executionId
,eventId
), but when an execution is running there's acorrelationId
field that will thwart any attempts to trigger another pipeline. This just strips out those junk fields when a re-run modal is mounted, which seems to do the trick.