I was just asked to reintroduce that error because the error prone version of the program was checked and was approved, but the fix is causing all this correctness that is throwing the numbers off and they no longer coincide with the flawed and incorrect way the program was checked. To recheck the correct version would delay the release.
I was told the correct version I created would be incorporated in the next release. The client is being told not to use the flawed feature in the release (which is the default, but he'll never use the default anyway. It's the default only because the regulatory bodies approving it require a default like this (although they did want a working default, but they're probably too dumb to find the flaw.))
Do you think this was a good decision?