Class: DefaultJobOptionsConfig
jobs/src.DefaultJobOptionsConfig
Constructors
new DefaultJobOptionsConfig()
new DefaultJobOptionsConfig():
DefaultJobOptionsConfig
Returns
Properties
backoff
backoff:
BackoffOptionsConfig
Backoff setting for automatic retries if the job fails
Source
libs/jobs/src/lib/config/default-job-options.config.ts:50
keepLogs
keepLogs:
number=0
Maximum amount of log entries that will be preserved Default 0, because we don't think that storing logs in redis is a good idea in general
Source
libs/jobs/src/lib/config/default-job-options.config.ts:83
lifo
lifo?:
boolean
If true, adds the job to the right of the queue instead of the left (default false)
See
https://docs.bullmq.io/guide/jobs/lifo
Source
libs/jobs/src/lib/config/default-job-options.config.ts:60
removeOnComplete
removeOnComplete:
KeepJobsConfig
Default behavior is up to 0 days and 0 jobs It allows us to do not have multiple jobs with the same type running in a cluster
Source
libs/jobs/src/lib/config/default-job-options.config.ts:67
removeOnFail
removeOnFail?:
KeepJobsConfig
Default behavior is 0 days and 0 jobs We do store this information in postgres, so redis doesn't make too much sense
Source
libs/jobs/src/lib/config/default-job-options.config.ts:74
sizeLimit
sizeLimit?:
number
Limits the size in bytes of the job's data payload (as a JSON serialized string).
Source
libs/jobs/src/lib/config/default-job-options.config.ts:101
stackTraceLimit
stackTraceLimit:
number=0
Limits the amount of stack trace lines that will be recorded in the stacktrace. Default 0, everything will be in logs if you need a stacktrace and should be for debugging, doesn't sound like a good idea to store in redis
Source
libs/jobs/src/lib/config/default-job-options.config.ts:93
Generated using typedoc-plugin-markdown and TypeDoc