Previously, our job queue system relied on `payload.*` operations, which ran very frequently: - whenever job execution starts, as all jobs need to be set to `processing: true` - every single time a task completes or fails, as the job log needs to be updated - whenever job execution stops, to mark it as completed and to delete it (if `deleteJobOnComplete` is set) This PR replaces these with direct `payload.db.*` calls, which are significantly faster than payload operations. Given how often the job queue system communicates with the database, this should be a massive performance improvement. ## How it affects running hooks To generate the task status, we previously used an `afterRead` hook. Since direct db adapter calls no longer execute hooks, this PR introduces new `updateJob` and `updateJobs` helpers to handle task status generation outside the normal payload hook lifecycle. Additionally, a new `runHooks` property has been added to the global job configuration. While setting this to `true` can be useful if custom hooks were added to the `payload-jobs` collection config, this will revert the job system to use normal payload operations. This should be avoided as it degrades performance. In most cases, the `onSuccess` or `onFail` properties in the job config will be sufficient and much faster. Furthermore, if the `depth` property is set in the global job configuration, the job queue system will also fall back to the slower, normal payload operations. --------- Co-authored-by: Dan Ribbens <DanRibbens@users.noreply.github.com>
85 lines
2.4 KiB
TypeScript
85 lines
2.4 KiB
TypeScript
import type { WorkflowConfig } from 'payload'
|
|
|
|
export const subTaskFailsWorkflow: WorkflowConfig<'subTaskFails'> = {
|
|
slug: 'subTaskFails',
|
|
inputSchema: [
|
|
{
|
|
name: 'message',
|
|
type: 'text',
|
|
required: true,
|
|
},
|
|
],
|
|
retries: 3,
|
|
handler: async ({ job, inlineTask }) => {
|
|
await inlineTask('create two docs', {
|
|
task: async ({ input, inlineTask }) => {
|
|
const { newSimple } = await inlineTask('create doc 1 - succeeds', {
|
|
task: async ({ req }) => {
|
|
const newSimple = await req.payload.create({
|
|
collection: 'simple',
|
|
req,
|
|
data: {
|
|
title: input.message,
|
|
},
|
|
})
|
|
|
|
const updatedJob = await req.payload.update({
|
|
collection: 'payload-jobs',
|
|
data: {
|
|
input: {
|
|
...job.input,
|
|
amountTask1Retried:
|
|
// @ts-expect-error amountRetried is new arbitrary data and not in the type
|
|
job.input.amountTask1Retried !== undefined
|
|
? // @ts-expect-error
|
|
job.input.amountTask1Retried + 1
|
|
: 0,
|
|
},
|
|
},
|
|
id: job.id,
|
|
})
|
|
job.input = updatedJob.input as any
|
|
|
|
return {
|
|
output: {
|
|
newSimple,
|
|
},
|
|
}
|
|
},
|
|
})
|
|
|
|
await inlineTask('create doc 2 - fails', {
|
|
task: async ({ req }) => {
|
|
const updatedJob = await req.payload.update({
|
|
collection: 'payload-jobs',
|
|
data: {
|
|
input: {
|
|
...job.input,
|
|
amountTask2Retried:
|
|
// @ts-expect-error amountRetried is new arbitrary data and not in the type
|
|
job.input.amountTask2Retried !== undefined
|
|
? // @ts-expect-error
|
|
job.input.amountTask2Retried + 1
|
|
: 0,
|
|
},
|
|
},
|
|
id: job.id,
|
|
})
|
|
job.input = updatedJob.input as any
|
|
|
|
throw new Error('Failed on purpose')
|
|
},
|
|
})
|
|
return {
|
|
output: {
|
|
simpleID1: newSimple.id,
|
|
},
|
|
}
|
|
},
|
|
input: {
|
|
message: job.input.message,
|
|
},
|
|
})
|
|
},
|
|
}
|