[Bug]: Issue with updating job template data with upsertJobScheduler

[erkkaha]

Version

5.29.1

Platform

NodeJS

What happened?

I have problem updating data with upsertJobScheduler.

With pattern the data is not updated. Data stays the same with each run.

With every the data is updated but for some reason the value of every is not respected
unless prevMillis is defined.

How to reproduce.

import { Queue, Worker } from "bullmq";

// Create a new connection in every instance
const myQueue = new Queue("myqueue", { connection: { host: "localhost" } });

const myWorker = new Worker(
  "myqueue",
  async (job: { data: any }) => {
    console.log(job.data);
    return upsert();
  },
  { connection: { host: "localhost" } }
);

const upsert = async () =>
  await myQueue.upsertJobScheduler(
    "my-scheduler-id",
    { pattern: "*/1 * * * *" },
    //{ every: 15000 },
    {
      name: "my-job-name",
      data: { ts: Date.now() },
      opts:{
        // prevMillis: Date.now()
      }
    }
  );

upsert();

Relevant log output

No response

Code of Conduct

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

[roggervalf]

hi @erkkaha, for the second case

With every the data is updated but for some reason the value of every is not respected
unless prevMillis is defined

it's because every option starts the first execution immediately by default when using job-schedulers

[erkkaha]

@roggervalf ok, Thanks for the reply. This seems to be the case regardless if immediately is used or not. Is this by design?

[roggervalf]

hey @erkkaha, yes that's by design. If you don't need to start a job immediately as every does. You can use pattern option with '*/15 * * * * *' expression as cron-parser supported cron expressions considering seconds as well https://www.npmjs.com/package/cron-parser. Let us know if that works for your case