Continue opening the session from file after an unexpected closure

What problem do you see this solving?
Discarding the request to open a .cosession file is disorienting.

When was the last time you were affected by this lack of functionality, or specific tool?
This happens when opening a .cosession file after an unexpected closure like BSoD, forced restart, or indeed a C1P crash: instead of the window with the requested session appearing after discarding the popup with a question whether I want to report unexpected closure, I get a generic window with a selection of recent sessions, which is irrelevant to the requested action. I have to close this window and open the file again, as there is likely no reference to the session I want to open on this list anyway, which is annoying and distracts from the flow.

Ignoring the request to open the file could backfire in case the crash reason is this "Most Recent" window, as there would be no way to go around it, no workaround, as it would be ALWAYS forced on user due to triggering the crash in loop. Continuing to open the .cosession file would allow to have an alternative approach to running Capture One in this case.

Are you using any workarounds or other solutions to achieve your goals in Capture One?
The workaround is to close Capture One and open the file again.

Are you happy to be contacted further about this suggestion or request?
Yes.