Currently, when rerunning a pipeline execution, the system utilizes the latest pipeline definition but retains the original inputs. However, this behavior makes it difficult to reproduce past pipeline executions, which is a recurring frustration for engineering teams. We are requesting the ability to rerun a pipeline with both the original pipeline definition and the original inputs, ensuring true reproducibility of past executions.

The feature could be implemented as a configuration option that allows users to choose whether to rerun with the latest or the original pipeline definition. For our account, we would prefer this configuration to default to the original pipeline definition. This enhancement would greatly improve debugging and provide more reliable historical execution reproducibility. We are hoping to have this feature included in the roadmap for Q4.