Today, in a pipeline execution that has multiple builds (e.g., re-runs under the same execution ID), the Supply Chain tab is only populated for the first build where SCS steps pass.

For later builds in the same execution, even when SCS steps succeed, the Supply Chain tab is either empty or not populated.

Users (devs, leads, managers) often open the latest run or a specific build and expect to see Supply Chain data there.

When the tab is empty for later builds, it looks like the scan didn’t run or the feature is broken.

This makes it confusing to use the Supply Chain tab as a reliable view of each scan run.

Make the Supply Chain tab available and populated for every build in an execution where SCS steps pass, not only the first successful build.

Each build view should show the Supply Chain info corresponding to that specific SCS scan run.

This would make Supply Chain views much more intuitive in real-world pipelines where re-runs and multiple builds per execution are common.