[Bug]: getRepeatableJobs() gives inactive repeatable jobs along (along with active repeatable jobs)

[vraj-fyno]

Version

v4.7.0

Platform

NodeJS

What happened?

Requirement

• I have added repeatable jobs with limit and then use getRepeatableJobs() to show active jobs and the next run time to the user
• The user should see if the repeatable job is active and the next run time

Expected

• getRepeatableJobs() would give only the active repeatable jobs
• or a parameter to get the same

Actual

• getRepeatableJobs() is currently giving all the repeatable jobs

How to reproduce.

Add data along with limits

const { Queue } = require("bullmq");

const connection = {
    port: process.env.REDIS_QUEUE_PORT,
    host: process.env.REDIS_QUEUE_HOST,
    password: process.env.REDIS_QUEUE_PASSWORD || "",
};
const EVENTQ_NAME = new Queue("campaign", {
    connection,
});

let repeatable = async () => {
    const test = await EVENTQ_NAME.add(
        "dynamite",
        { color: "black" },
        {
            repeat: {
                pattern: "* * * * *",
                limit: 10,
            },
        }
    );
    console.log(test.repeatJobKey);
};

repeatable();

See the repeatable jobs after the above is consumed by a worker

const { Queue } = require("bullmq");

const connection = {
    port: process.env.REDIS_QUEUE_PORT,
    host: process.env.REDIS_QUEUE_HOST,
    password: process.env.REDIS_QUEUE_PASSWORD || "",
};
const EVENTQ_NAME = new Queue("campaign", {
    connection,
});

let repeatable = async () => {
    const repeatableJobs = await EVENTQ_NAME.getRepeatableJobs();
    console.log(repeatableJobs);
};

repeatable();

Relevant log output

[
  {
    "key": "campaign:CAPVUXP4P::Asia/Kolkata:* * * * *",
    "name": "campaign",
    "id": "CAPVUXP4P",
    "endDate": null,
    "tz": "Asia/Kolkata",
    "pattern": "* * * * *",
    "next": 1705057500000
  }
]

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[vraj-fyno]

In the bull monitor, there is no data in the delayed queue

[manast]

Currently this works as expected, however I see it could be useful to have a feature to filter out repeatable jobs that have expired, or that they get "auto removed" after they expire.

[vraj-fyno]

Thanks! Yeah, it would be a great feature to have.