People usually don't see the history of these kind of systems.
In most cases these issues are a result of similar kind of patching of a previous similar issue resulting in unexpected outcomes. (Probably going on for years)
From my experience management often tries to ignore the bigger refactors by using inexperienced people to patch things repeatedly, meanwhile the team suffocates under technical debt and responsibilities as a result of this mentality.
Sometimes its better to stick with the dev team for long term goals instead of becoming a "management puppet" for short term wins.
In most cases these issues are a result of similar kind of patching of a previous similar issue resulting in unexpected outcomes. (Probably going on for years)
From my experience management often tries to ignore the bigger refactors by using inexperienced people to patch things repeatedly, meanwhile the team suffocates under technical debt and responsibilities as a result of this mentality.
Sometimes its better to stick with the dev team for long term goals instead of becoming a "management puppet" for short term wins.