Here's how to handle the situation you are in right now: 1. Work with the team to identify what item in the current sprint will be delayed. 2. The EM and Scru

Here's how to handle the situation you are in right now: 1. Work with the team to identify what item in the current sprint will be delayed. 2. The EM and Scrum Master should communicate the delayed issue to their leadership. 3. Identify any long-term objective that will be delayed and communicate that as well. If there's a question about why a delay will occur be honest: either the critical issue affecting customers gets fixed now, or the new thing customers don't yet have gets attention. Going forward, allocate 1 day per person in each sprint as capacity to address bugs. Do this explicitly if you have mature leadership who understand how development works, or implicitly by padding other estimates if you haven't. Addressing bugs should be an implied task every sprint. When there are no important and urgent bugs, that capacity should be used to address tech debt instead.