Yes, this is an issue that we've consistently encountered during testing and it's always at this specific part. Right now we're looking into fixing it permanently but as of now, there's nothing in the code that we can detect would cause it so we're still finding the root cause of the bug!