@freezing-airport-6809 as a part of run we are using Flyte execution Id and creating the a table Job audit where store details of the run, the configs that were used, how many row processes input and output and so on. This helps us to provide a bird eye view of holistically understand run, restart or use tables as source and run the data for a particular execution id 1 or more than 1 . Ex we ran a flow which loaded Table A,B,C. We can use TableB as source and it can be used to select all data for a particular execution.