Re: 41 hours of latency sounds bad...
In my first job, we had overnight batch runs, but there were frequent errors with the cards at the start and the end of each batch job not being set up correctly. I wrote a clever trick (can't remember how it worked now) which meant that the start/end card errors were reduced by 90%.
Which meant that a lot more high priority jobs ran correctly far more often.
Which meant that my low priority jobs frequently didn't get time to run overnight - which meant I often had to wait 36 hours for my job to be returned.
Talk about being punished for doing the right thing...
Biting the hand that feeds IT
