In Directed Acyclic Graph (DAG) pipelines, where stages are linked by dependencies and can run in parallel, any stage can be chosen in "Re-run From Specific Stage" or "Retry Failed Stages". If a downstream stage is selected on its own, the stages before it are replayed from the previous execution, so it consumes stale outputs and variables from upstream instead of fresh ones. For pipelines with many cross-stage dependencies, this can produce inconsistent or invalid runs.

We'd like a setting in the pipeline or template configuration (for example a "Re-run Settings" section under Advanced Options) to define which stages are allowed as re-run or retry starting points. Stages not on the list would be disabled or hidden in the re-run dialogs. Today RBAC and OPA can't enforce this, and the only related ideas disable re-run entirely, which is too coarse when some stages are safe to restart and others aren't.