Your question is Launch With Unresolved Solution Risk. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You are leading the launch of a new control-plane feature for a managed cloud service. The feature is functionally complete, but the team is split on whether the failure modes are fully understood: one service dependency has only partial test coverage, a small but real percentage of requests still hit a fallback path, and the support team is worried about customer impact if the issue appears after launch. At the same time, the business wants to hit a committed launch window, and delaying it would affect a partner announcement already in motion.
How do you handle a situation where a launch needs to happen but the team is not fully confident in the solution?