Last modified: 2014-04-17 10:30:54 UTC
In the default configuration, jobs that fail to run for any reason simply build up in the job table and are never cleared. The facility exists to do so via the claimTTL parameter, but this is set to zero by default. I don't believe there's any reason a job can't be re-attempted in a standard configuration, so this should probably be set to a non-zero value when the job queue object is initialized.