FlowProducer does not use defaultJobOptions from specified queue.

[arthurvanl]

So I have a queue setup and a FlowProducer.

I use the FlowProducer#addChain fn and each step has a name, queueName & data props

In the queue I setup the defaultJobOptions with a repeat of 1000ms

However it seems that it does not run again.

There is an option to set opts per step. But I want this to be set per queue (not per step)

Also this opts raised me another question, what if a step has finished but it did not reach the last step of the chain. Will it start a new job including the same chain (when it's a repeated job) ?

[egeominotti]

Hey, thanks for the detailed report!

I investigated this and here's what's happening:

1. defaultJobOptions is not applied to FlowProducer jobs

This is a current limitation. When you use Queue.add(), defaultJobOptions is merged with per-call options. However, FlowProducer#addChain only uses step.opts — it does not read or merge defaultJobOptions from the queue.

So even if you set repeat: { every: 1000 } in defaultJobOptions, it won't be applied to chain steps.

Workaround for now: set repeat explicitly in each step's opts:

await flow.addChain([
  { name: 'step1', queueName: 'myQueue', data: {}, opts: { repeat: { every: 1000 } } },
  { name: 'step2', queueName: 'myQueue', data: {}, opts: { repeat: { every: 1000 } } },
]);

2. Repeat does NOT re-create the entire chain

When a job with repeat completes, the server creates a new standalone job with the same data/options. But it does not re-create the chain dependencies. This means:

• Step 1 completes → a new Step 1 is created (repeated), but it's independent
• Step 2 will not be triggered again because it depended on the original Step 1's ID

So to answer your question: if a step finishes but the chain hasn't completed yet, the repeated job starts as an isolated job, not a new chain.

3. To repeat an entire chain, use a cron job

If you need the full chain to run on a schedule, use a cron job that calls addChain periodically instead of relying on repeat:

await queue.upsertJobScheduler('my-pipeline', {
  every: 1000,
}, {
  name: 'pipeline-trigger',
  data: {},
});

Or use the cron API to schedule periodic chain creation.

---

I'll track both of these as improvements:

• Support merging defaultJobOptions into FlowProducer steps
• Consider a repeat option at the flow/chain level that re-creates the entire chain

Thanks for raising this!

[arthurvanl]

Oke i will start using the upsertJobScheduler to solve this issue.

Which will add the chain. And that also allows me to check it an old job is still running. Thanks for showing this!