Creating jobs with upsertJobScheduler and every running twice after creation

[PhenomEY]

Hey,

i noticed that jobs created through the upsertJobScheduler are running twice in a row.
The first one runs immediately, which is fine but after the creation it runs a second time after completion

how can i prevent this behaviour? the immediately parameter is deprecated so it doesnt work to set it to false.

I want the scheduled job to run immediately after creation but the next execution should follow the given every parameter

Best regards

[manast]

@PhenomEY do you have a test case where the scheduler behaves as you described? is should currently work as you wanted it to work, so if that is not the case then it is a bug.

[PhenomEY]

@manast

I do the following to create the job:

    const myQueue = new Queue('queueName', {
        connection: {
            host: process.env.REDIS_HOST,
            port: parseInt(process.env.REDIS_PORT),
        },
        defaultJobOptions: {
            removeOnComplete: {
                age: 3600
            },
            removeOnFail: {
                age: 24 * 3600
            }
        }
    })

    await myQueue.upsertJobScheduler(
        'my-scheduled-job',
        {
            every,
        },
        {
            name: 'my-scheduled-job',
            data: { mydata },
            opts: {
            }, 
        },
    );

My worker:

        const worker = new Worker('queueName', async (job: TJob) => {
           //todo: handle job
        }, this.connection);

        // handle errors
        worker.on('completed', (job: TJob) => {
            console.log(job.id)
            console.log('completed')
        })

console:
repeat:5019d1af-13da-443d-9bb3-75abbd5b7200-69f7d36c-3f81-4a0e-a1d0-fd837ad3bf1e:1762421484062
completed
repeat:5019d1af-13da-443d-9bb3-75abbd5b7200-69f7d36c-3f81-4a0e-a1d0-fd837ad3bf1e:1762416000000
completed

[PhenomEY]

well i was still using v5.52 - updating to 5.62.2 fixed this