Ahh, another 32 bit overflow problem. I still think I'll be making big bucks after my retirement working on the Y2038 epoch overflow problem [1], just as COBOL programmers were reportedly in high demand for Y2K.
I confess to having committed this sin. The order tracking at my employer suddenly started crashing during load and this happened when I was on the other side of the world with only e-mail access.
The culprit turned out to be a Y2K38 bug on my part triggered by a salesman fat-fingering an order into the 2060s. The only Y2K bug I had wasn't worth fixing--one list of reports was "date"-sorted (dates in the filenames) and making the display wider was more of a downside than dealing with the mis-sort at rollover.
[1] https://en.wikipedia.org/wiki/Year_2038_problem