Workers not firing the completed event

[ryandotelliott]

I'm trying to use Express in combination with delayed jobs in Bull. The jobs seem to be scheduled appropriately, however, it appears that after being executed not all workers first a completed event.

My worker is setup as follows:

const worker = new Worker(
    "welcomeMessages",
    async (job: Job) => {
        console.log(`Started job ${job.name} at ${new Date().getTime()}`);

        switch (job.data.type) {
            case ScheduledJobType.MY_EXAMPLE_JOB: {
                console.log("Hello from the JOB!");
                break;
            }
        }
        return true;
    },
    {
        connection: redisConnection,
        concurrency: 5,
    }
);

I have a simple completed listener similar to the following:

worker.on("completed", async (job) => {
    console.log(`Completed job ${job.name} at ${new Date().getTime()}`);

    if (!job?.id) {
        console.log("Failed to mark job as completed, job id is null");
        return;
    }
});

When scheduling two events for the same time, one of the events is process and executes the completed event correctly, but the other seems to "silently" complete. This silent completion results in the job being marked as completed, the queue being set to drained, but the actual completed handler not being called.

Does anyone know what might be wrong here? Feel free to ask for any other information if necessary.

[ryandotelliott]

🤦‍♂️ Turns out I had a separate client connected to the queue on a server running an older version of the code. I was using Redis Cloud and thought i had disabled it on the server, but the pm2 instance was running on sudo.. Dumb mistake, but maybe someone else will be saved.