@futurebird Maybe some direct instruction troubleshooting lessons?
Distribute code broken in specific ways and show them how to tell which problem is showing up?
The calling out is definitely contageous, I recognise that. Can you structure in class troubleshooting time as you go - perhaps each kid has a visual token so you can see at a glance who needs help and who can give it? Something like a card with different colours front and back for 
/
?