I've repeatedly run into the issue where a transaction or a session crashed while a SAT measurement is running. Unfortunately, some measurements take a long time, so a considerable amount of work is lost. But the trace is actually there, and very likely perfectly usable. It's just not accessible because SAT still thinks the measurement is still running, which it clearly is not (the user transaction is gone). Unfortunately "stop active measurements" doesn't help either (it just says "0 measurements stopped"). How can I salvage that trace? Isn't there a way to tell SAT that the measurement is indeed over and it should at least try to use the trace as-is?
