There’s no way to salvage the data & disposition. In fact there should be even more of a disruption in Scripter than described – when Scripter loses its connection to SessionManager it should actually close down. That’s a hold-over from the old Win32 behavior and something we should probably improve upon.
Even if we kept Scripter open and somehow kept the script open though, the Dialer process on CIC2 has no knowledge of the agent or of the contact they’re connected to.
In 4.0 we’re adding record binding and one of the proposed uses of it is to improve our behavior in this scenario, because it allows us a way to have Dialer pick up on that outstanding contact and load it into cache on the fly, so it could then accept a disposition for it. Of course the other part of the puzzle is getting Scripter to stay open and preserve the script and its data, which would present a few challenges.