In the Console go to Reports > All Reports > Software > Delivery > Execution Status.
Note that the report parameter "Software Delivery Instances to Include" has three options: "All", "Only First for Computer" and "Only Most Recent for Computer".
This parameter works for Quick Delivery tasks, and probably Package Delivery tasks but I did not test that.
However, this parameter does not work for Managed Software Delivery (MSD) policies.
To test I ran an MSD policy twice on one computer, fifteen minutes apart.
Both runs were successful.
The Evt_AeX_Software_Execution table shows both run instances.
However, the Execution Status report only shows the most recent run instance.
It shows the most recent run instance regardless of which option is selected in the "Software Delivery Instances to Include" parameter.
I also tested with a Quick Delivery (QD) task.
When the "Software Delivery Instances to Include" parameter is set to "All" it displays both run instances of the QD task.
When the parameter is set to "Only First for Computer" it shows the first run instance.
When the parameter is set to "Only Most Recent for Computer" it shows the most recent run instance.
Of course the date range on the report was set to include all run instances of both the MSD policy and QD task. All other parameters were left at the default values.
The Execution Status report calls the stored procedure sp_GetSoftwareDeliveryExecutionStatus. That stored procedure calls the vSMS_SoftwareExecutionStatus2 view. That view calls the
Inv_AeX_SWD_Execution_Summary table for MSD policies. That table only contains the most recent instance of each policy per client computer (resource guid).
However, for Quick Delivery (QD) and Package Delivery (PD) tasks the vSMS_SoftwareExecutionStatus2 view calls the Evt_Task_Instances table. That table also only contains one instance of each task per client computer (resource guid). Yet the Execution Status report shows all the instances of a QD task, I did not test PD tasks but they would probably display the same as QD tasks.
This is a known issue.
This issue will be addressed in version 7.6 HF1.
One customer corrected this by replacing the join with the Inv_AeX_SWD_Execution_Summary table with a join with the Evt_AeX_SWD_Execution table in the vSMS_SoftwareExecutionStatus2 view.
Reported and confirmed on 7.5 HF5 and HF6.
May also apply to other versions.