I’ve seen it before. If you’re not actually deploying twice at the same time it could just be a passing issue. I’ve had to just wait it out before