Jobs and Results are stored separately in Redis, with the Job ID being the link between them. When clearing failed Jobs, the code iterates one-by-one over these Jobs and calls the delete() method on them. This correctly removes the Job keys from Redis, but it effectively orphans the Result keys, which then never get cleaned up and end up just holding memory space.
Expectation: deleting a failed Job should also delete all Results for that Job.
Jobs and Results are stored separately in Redis, with the Job ID being the link between them. When clearing failed Jobs, the code iterates one-by-one over these Jobs and calls the delete() method on them. This correctly removes the Job keys from Redis, but it effectively orphans the Result keys, which then never get cleaned up and end up just holding memory space.
Expectation: deleting a failed Job should also delete all Results for that Job.