Named jobs in NestJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a named job is added twice with the same name?

Consider a NestJS Bull queue where you add a named job twice with the same name but different data. What will be the behavior?

NestJS

await queue.add('email', { to: '[e-mail]' });
await queue.add('email', { to: '[e-mail]' });

A The second job replaces the first job in the queue.

B Both jobs are added separately and processed independently.

C Only the first job is added; the second is ignored silently.

D An error is thrown because job names must be unique.

💡 Hint

Think about how queues handle jobs with the same name but different data.

Named jobs in Bull are just labels. Adding two jobs with the same name but different data creates two separate jobs. They are processed independently in the order they were added.

📝 Syntax

intermediate

Which code correctly adds a named job with repeat options in NestJS Bull?

Choose the correct syntax to add a named job called 'cleanup' that repeats every hour.

A await queue.add('cleanup', {}, { repeat: { cron: '0 * * * *' } });

B await queue.add({ name: 'cleanup', data: {}, repeat: { cron: '0 * * * *' } });

C await queue.add('cleanup', {}, { repeat: '0 * * * *' });

D await queue.add('cleanup', { repeat: { cron: '0 * * * *' } });

💡 Hint

Remember the method signature: add(name, data, options).

The correct syntax uses the job name as the first argument, job data as the second, and options (including repeat) as the third argument.

🔧 Debug

advanced

Why does this named job never run in NestJS Bull?

Given the following code, why does the named job 'processData' never execute?

NestJS

queue.process('processData', async (job) => {
  console.log('Processing:', job.data);
});

await queue.add('processdata', { id: 1 });

A The process() method is missing a concurrency parameter, so it never runs.

B The job data is missing required fields, so the job is skipped.

C The job name in add() is lowercase 'processdata', but process() listens for 'processData' (case mismatch).

D The queue is not started, so no jobs run.

💡 Hint

Check the exact spelling and casing of job names.

Job names are case sensitive. The job was added with name 'processdata' but the processor listens for 'processData'. They do not match, so the job is never processed.

❓ state_output

advanced

What is the job count after adding and removing named jobs?

Consider this sequence:

await queue.add('task1', {});
await queue.add('task2', {});
const job = await queue.getJob('task1');
await job?.remove();
const count = await queue.count();

What is the value of count?

A 2

B Throws an error because getJob expects a job ID, not a name.

C 0

D 1

💡 Hint

Check the parameter type expected by getJob().

The getJob() method expects a job ID, not a job name. Passing a name returns null, so job?.remove() does nothing. The count remains 2.

🧠 Conceptual

expert

How does Bull handle concurrency for named jobs in NestJS?

In NestJS Bull, if you define multiple processors for the same named job with different concurrency values, what happens?

A Bull throws an error because multiple processors for the same job name are not allowed.

B Bull uses the highest concurrency value among processors for that job name.

C Only the first registered processor runs; others are ignored.

D Bull runs all processors in parallel, each with its own concurrency setting.

💡 Hint

Think about how Bull distributes jobs to processors.

Bull allows multiple processors for the same named job. Each processor runs independently with its own concurrency. Jobs are distributed among them.

Practice

1. What is the main benefit of using named jobs in NestJS queues?

easy

A. They automatically speed up job processing.

B. They help identify and manage specific background tasks easily.

C. They encrypt job data for security.

D. They allow jobs to run without a queue.

Solution

1. Step 1: Understand the purpose of named jobs

   Named jobs provide a clear label to background tasks, making them easier to find and manage.

2. Step 2: Compare options with the purpose

   Only They help identify and manage specific background tasks easily. matches this purpose. Options B, C, and D describe unrelated features.

3. Final Answer:

   They help identify and manage specific background tasks easily. -> Option B

4. Quick Check:

   Named jobs = easier management [OK]

Hint: Named jobs label tasks for easy tracking [OK]

Common Mistakes:

• Thinking named jobs improve speed
• Confusing named jobs with security features
• Assuming named jobs remove the need for queues

2. Which of the following is the correct way to add a named job to a queue in NestJS?

easy

A. queue.pushJob('emailJob', { to: '[e-mail]' });

B. queue.createJob('emailJob', { to: '[e-mail]' });

C. queue.runJob('emailJob', { to: '[e-mail]' });

D. queue.add('emailJob', { to: '[e-mail]' });

Solution

1. Step 1: Recall the NestJS queue method for adding jobs

   The correct method to add a job with a name is queue.add(name, data).

2. Step 2: Match the method with options

   Only queue.add('emailJob', { to: '[e-mail]' }); uses queue.add with a job name and data correctly.

3. Final Answer:

   queue.add('emailJob', { to: '[e-mail]' }); -> Option D

4. Quick Check:

   Use queue.add(name, data) [OK]

Hint: Use queue.add('jobName', data) to name jobs [OK]

Common Mistakes:

• Using non-existent methods like createJob or pushJob
• Forgetting to pass the job name as first argument
• Confusing job execution with job creation

3. Given this code snippet, what will be the output when checking the job name?

const job = await queue.add('reportGeneration', { userId: 42 });
console.log(job.name);

medium

A. 'reportGeneration'

B. 'default'

C. undefined

D. Throws an error

Solution

1. Step 1: Understand job creation with a name

   When adding a job with queue.add('reportGeneration', data), the job's name property is set to 'reportGeneration'.

2. Step 2: Check the console.log output

   Logging job.name will print 'reportGeneration'.

3. Final Answer:

   'reportGeneration' -> Option A

4. Quick Check:

   Job name property = 'reportGeneration' [OK]

Hint: Job.name matches the string passed to queue.add [OK]

Common Mistakes:

• Assuming default name is used if a name is given
• Expecting undefined if name is not accessed properly
• Thinking job creation throws error without processor

4. Identify the error in this NestJS queue job addition:

queue.add({ name: 'cleanupJob' }, { force: true });

medium

A. Job name should be a string, not inside an object.

B. The second argument must be a string, not an object.

C. The method add() does not exist on queue.

D. The job data cannot contain boolean values.

Solution

1. Step 1: Review the correct syntax for named jobs

   The queue.add method expects the first argument as a string name, not an object.

2. Step 2: Analyze the given code

   The code passes an object { name: 'cleanupJob' } instead of a string, causing a syntax error.

3. Final Answer:

   Job name should be a string, not inside an object. -> Option A

4. Quick Check:

   First argument to add() = string name [OK]

Hint: Pass job name as string, not object, to queue.add [OK]

Common Mistakes:

• Passing job name inside an object instead of string
• Confusing job data with job name argument
• Assuming add() method is missing or invalid

5. You want to cancel all jobs named 'emailNotification' in a queue. Which approach correctly uses named jobs to achieve this?

hard

A. Restart the queue to clear all jobs named 'emailNotification'.

B. Call queue.removeJobs('emailNotification') directly without fetching jobs.

C. Use queue.getJobs(['emailNotification']) and then call remove() on each job.

D. Filter jobs by data property { type: 'emailNotification' } and delete them.

Solution

1. Step 1: Understand how to retrieve named jobs

   Named jobs can be fetched using queue.getJobs(['jobName']) which returns jobs with that name.

2. Step 2: Remove each fetched job

   After fetching, calling remove() on each job deletes them from the queue.

3. Final Answer:

   Use queue.getJobs(['emailNotification']) and then call remove() on each job. -> Option C

4. Quick Check:

   Fetch named jobs then remove [OK]

Hint: Fetch named jobs first, then remove them one by one [OK]

Common Mistakes:

• Trying to remove jobs by name without fetching them
• Filtering jobs by data instead of name
• Restarting queue does not selectively remove jobs