That sounds like something that should hopefully be resolved when the backend overhaul is implemented in a few months, but for now try playing through that part with QTEs turned off (available in the options screen). It may fix itself after progressing through that segment.