If a customer resumes a failed pipeline it creates a second execution and keeps the firsts execution in the history. The “Tests” and ”Security Tests” data are only accessible from the build execution that actually contained the step that created the data. In the case of multiple resumes, this might mean you have data scattered throughout the build history and no data, or incomplete data, associated with the final run.

Customer wants to be able to see this data without going through the history and in cases where the data has been split across multiple executions, they would want to see it aggregated together as though all of it had been created in the final execution.