If scores are important to meeting a team’s personal goals or bonuses, I could understand their hesitation to collect transactional web feedback in the middle of an update. However, I think collecting scores throughout the process could be good because you can see if there are any other things that need to be fixed besides the already known kinks. It could also be helpful to understand how metrics differ before and after the known issues are fixed. 

Thanks @ash123 !  Very aligned in our thinking but wanted to hear from others.  I appreciate your reply.

@Alysson DuPont Survey & Dashboard is for Measuring & Monitoring so by best practice you should have some CX action that gonna give you something to evaluate before/after effect beside finding new opportunity for improvement. That’s closing the loop of Listen → Analyze → Act. So this is your time for Collecting feedback.

However, by surveying you’re spending money to gather hidden insight that gonna fuel your next action. There’s an obvious problem here and it’s being hotfixed (happened a lot with new app) so majority of your response will just point-out the obvious and being wasted. Also, if you let this slide, the IT team will be deeply grateful, but make sure the problem got fixed quickly.

You can still launch survey focus on other newly update feature.
Hope this helps