Good news - I'm fairly certain that I've managed to find and fix this issue. It wasn't easy, haha. I still have to have it run through our beta testing team, but I think it should be fine. The fix will be in MixEmergency 3.0.2 (which will be released when it's ready).