You need to choose your rabbit holes carefully. In large and complex codebases, its often more pragmatic to build a guard in your local area against that bug,

You need to choose your rabbit holes carefully. In large and complex codebases, its often more pragmatic to build a guard in your local area against that bug, than following the bug all the way downthe stack. Its not optimal, and doesn't make the system better as a whole. but its the only way to get things done. That doesn't mean you should be silent though, you do need to contact the team that looks after that part of the system