How do you pass a custom REQUEST object to a REQUEST-scoped provider for queues or CRON jobs in NestJS?

Difficulty: 7/10

Request scope, Dependency injection, Background jobs

Use ContextIdFactory.create() to generate a custom context ID, then call moduleRef.registerRequestByContextId() to bind a synthetic request object to it. Resolve the REQUEST-scoped provider using that context ID so it receives the synthetic request instead of a real HTTP request.

Queue processors and scheduled jobs have no HTTP request, but you may still need REQUEST-scoped providers for per-job isolation (e.g., tenant context per job). The solution is to synthetically create a request-like context for each job execution.

Custom request context for a queue processor

Use cases:

1
Bull/BullMQ queue processors — per-job tenant isolation.
2

How do you pass a custom REQUEST object to a REQUEST-scoped provider for queues or CRON jobs in NestJS?

Difficulty: 7/10

Request scope, Dependency injection, Background jobs

Use ContextIdFactory.create() to generate a custom context ID, then call moduleRef.registerRequestByContextId() to bind a synthetic request object to it. Resolve the REQUEST-scoped provider using that context ID so it receives the synthetic request instead of a real HTTP request.

Custom request context for a queue processor

Use cases:

1
Bull/BullMQ queue processors — per-job tenant isolation.
2

How do you pass a custom REQUEST object to a REQUEST-scoped provider for queues or CRON jobs in NestJS?

Use ContextIdFactory.create() to generate a custom context ID, then call moduleRef.registerRequestByContextId() to bind a synthetic request object to it. Resolve the REQUEST-scoped provider using that context ID so it receives the synthetic request instead of a real HTTP request.

How do you pass a custom REQUEST object to a REQUEST-scoped provider for queues or CRON jobs in NestJS?

Use ContextIdFactory.create() to generate a custom context ID, then call moduleRef.registerRequestByContextId() to bind a synthetic request object to it. Resolve the REQUEST-scoped provider using that context ID so it receives the synthetic request instead of a real HTTP request.

Scenario Questions

Follow-up Questions