It can take quite a lot of time track why something went wrong. I have spent months looking for bugs in systems. The software guys are the worst, when
something goes wrong on a new system, it is ALWAYS the hardware that is at fault, and then the poor hardware developer has to prove that his hardware
is working as it should before the software guys would even start looking at their code.
Some software systems gets so complicated, that a whole team of programmers work on it, and it is quite easy to miss bugs. Even in military or
avionics or space systems, where the code has to be certified, quite a number of bugs still get through the process.
Sometimes it is not even a real bug, i.e. faulty code, but just a weird interaction of software and hardware, that only happens under very specific
conditions, and to find those errors can take months (if ever).
How many other space probes had to be reprogrammed in space, or how many other space probes failed as a result of software? A LOT
, I am just happy
that they managed to find the bug, because now they can start working on their next probe
