Thank you for this. I was able to find a typo in one of the variables which caused this issue to occur in certain instances. After the event, and before entering the Missions screen, go to one of the other screens (such as Information, Interact, or Memories) and then exit out. This will correctly reset the variable and bypass this error. I will ensure this bug is fixed for the next release.