does not matter how you were connected, there is a BUG in sparrow 2.3.0 which causes this behavior. Sparrow already fixed the bug, but haven't released it yet (should be out next week or so). Downgrade your sparrow, as mentioned in the twitter post, or wait for new release. Q didn't "loose" anything & same thing would happen to you if you use Mk4 with sparrow 2.3.0