Hmm haven't encountered that one yet, but I have the build open as of typing so I'll look into it before releasing the update today. Thanks for bringing this to my attention!
EDIT: Hey I took a look and tested that section myself, didn't have any issues but I did add a timer that should "force" that section along as a kind of safety net in case the code should fail at that sequence again. Hopefully shouldn't happen anymore :D