Seeing jobs dequeued/run multiple times for long-running cron jobs, despite same jobId/start time about work HOT 3 OPEN

I think you should use this middleware to wrap your enqueuer: https://pkg.go.dev/github.com/taylorchu/[email protected]/middleware/unique.

It maps a job into a unique key and a unique duration.

The way how you did it will have race conditions.

from work.

Thank you so much for the fast response! The issue is, we have varying jobs already in existence that will require different unique durations (i.e. the cron job above runs daily, but others run every 3 days). Is there a non-duration solution? For example, is it possible to just base it off of whether the job ID is unique and whether a job with that same ID is currently in the queue?

Or if we are going about this incorrectly, what is the best way to proceed?

from work.

uniq function can switch by enqueue options https://pkg.go.dev/github.com/taylorchu/[email protected]#EnqueueOptions too.

from work.