Forever active jobs after Kue terminated and recovered

We are trying too build a fault-free solution for jobs. We have tested and found that if we halt Kue or node in the middle of jobs processing then these jobs are never done after Kue/node recovered. These jobs are in forever active status. Do you plan to solve this problem, i.e. re-queue active jobs on start?

Start by reproducing a Kue or Node.js halt while jobs are processing, then inspect the startup and active-job recovery paths. Done means jobs left active by termination are re-queued after recovery and the behavior is covered by a regression test; the issue names no specific files or existing tests.

Written by the indexing model from the issue text.