Yeah. Let's see if I can explain this whilst still keeping the mysteriousness of Redacted, Inc intact.
So, we have lots of clients. They send us information every day. In the wee hours of the morning, we have to process that information in one big burst - so this daily processing is basically the primary reason for our existence. It kicks off automatically, but if certain things happen in the code, it can completely break the processing. Heck, sometimes our clients sending us corrupted data can cause the whole thing to break down, which is always fun.
So there's definitely nothing there that anybody would be killing on purpose because it was running too long. It's a big job that usually takes several hours to run, so they're used to that. It's just that there are a lot of moving parts and a huge amount of data, and that means that little changes can cause things to break.
Especially fun is when they break things without believing us at first. We'll say, "Hey! This thing is broken!" And they'll say, "What? We didn't do anything that could affect that!" And then it will turn out that the thing they did indeed affected it. And they'll go, "Oh. Oops."