I know what you're saying but, how is a computer supposed to know when it is truly a "failed print job"?

One example of why deleting a print job after a set amount of time might not be the solution you're looking for. Let's say you have the computer setup to delete a failed print job two minutes after it receives a printer error. (You could set it for longer of course but you don't want your mother to get impatient and call you.):
  • So, your mother sends something to the printer and runs to the restroom.
  • The printer gets a paper jam and sends an error signal the computer.
  • The computer pops up an error message and starts counting down.
  • After two minutes, the computer deletes the print job.
  • Your mother comes back and removes the paper jam.
  • And now, because her print job isn't printing, she calls you.
I know you're probably thinking well, I'll just have to set it a bit longer, say 10 minutes, and tell her she'll just have to be patient.

So, she now sends a print job to the printer and goes to the grocery store, or to bed. The printer runs out of ink and signals the computer. The computer waits 10 minutes and deletes the print job. She gets back, replaces the ink cartridge and then when nothing prints, yep, you guessed it, she calls you ... again.

There might also be a case where you would never want the computer to delete a print job. Let's say she was attempting to print a receipt with the all-important confirmation number for a transfer of $99,999.99 she just made into your savings account . . . and yep, the printer jammed, or ran out of ink, or whatever. Are you *-s-u-r-e-* you would want the computer to decide to delete this print job?