Hey @Rizzi, sorry for the late reply here!
I was able to confirm that this is not a bug but rather how runs have worked since the start of our Fatigue Detection system. However, this is now causing an “issue” with the ability to see what impact they have on the future. All of this to say, this is not how we want it to work permanently, but I don’t have an ETA of when we’ll change it