#2960 [UI Feature] Relaunch/recover execution with same clusterPool as original execution Issue created by iaroslav-ciupin Motivation: Why do you think this is important? flyteidl was recently updated to support specifying cluster pool when creating new execution. We need to make sure when we recover/relaunch execution, same cluster pool is sent in CreateExecution request. Goal: What should the final outcome look like, ideally? On hitting relaunch/recover button, new CreateExecution request must take same cluster pool as original execution. Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte