That response is reasonable IMO, as who knows what goes on behind the scenes. As long as it is passed on to the engineering group, that is a start.
If this issue could be solved by a simple configuration fix, we likely would have found it by now. This issue started with IRST 11.6, and if you check the release notes, you'll see there is quite a bit going on.