A Stopped Run Is Not a Finished Run
A half-filled sheet should say whether you called stop or the other side only answered half.
A Lookout comparison run can be cancelled midway. Cancelled is now a status of its own rather than reading as Completed; billing covers only the combinations checked before the cancel, their report stays downloadable, and Retry guards against starting the same job twice.
A revenue manager sets up a Lookout comparison for a group of hotels, notices halfway through that the date range is wrong, and presses cancel. A run is made of many combinations: one hotel, one set of stay conditions and one supplier make one price check. At the moment of cancelling, some combinations are done and others have not started.
Afterwards, someone has to read that run. If a run stopped halfway is labelled Completed, it looks exactly like a run where suppliers only returned half the results. One was your decision, the other a problem on the supplier side. They lead to different conclusions in analysis, and they make billing conversations murky.
Cancelled became a fourth status in the results list, next to Running, Completed and Failed, with its own filter. Folding it into Completed would have kept the list simpler; a separate state keeps the reading honest, and that is the one we chose. Billing has not changed: only combinations checked before the cancel are charged, their report can still be downloaded, and the cancel dialog now says so plainly.
One more detail sits on the result page. Retry cannot be pressed again until its request has come back, and it stays disabled once a new run has started. A second start of the same job from anywhere else is refused as well, because a job can have only one active run at a time.