interface JobQueueOptions {
  jobQueueStrategy?: JobQueueStrategy;
  jobBufferStorageStrategy?: JobBufferStorageStrategy;
  activeQueues?: string[];
  enableWorkerHealthCheck?: boolean;
  prefix?: string;
}

Defines how the jobs in the queue are persisted and accessed.

Defines the queues that will run in this process. This can be used to configure only certain queues to run in this process. If its empty all queues will be run. Note: this option is primarily intended to apply to the Worker process. Jobs will always get published to the queue regardless of this setting, but this setting determines whether they get processed or not.

When set to true, a health check will be run on the worker. This is done by adding a check-worker-health job to the job queue, which, when successfully processed by the worker, indicates that it is healthy.

Important Note: This health check is unreliable and can be affected by existing long running jobs, see this issue for further details. For this reason, the health check will be removed entirely in the next major version.

Prefixes all job queue names with the passed string. This is useful with multiple deployments in cloud environments using services such as Amazon SQS or Google Cloud Tasks.

For example, we might have a staging and a production deployment in the same account/project and each one will need its own task queue. We can achieve this with a prefix.