feature-request: It should be possible to predict a job key or id.

[nuelsoft]

There are cases where an actor would want to replace an already scheduled job. The current solution doesn't allow for this or any kind of job filtering by data jsonb object.

An example use-case

function schedulePendingActionNotificaion(userId: string) {
  const queue = 'pending-actions-notifcation'
  const key = `pending-action::${userId}`
  boss.cancel({name: queue, key})
  boss.send(queue, {userId}, { key })
}

This doesn't have to replace the existing id, It should only another possible reference that can be predicted uniquely

[jorinvo]

It would be sufficient if pg-boss allows passing an id to send() instead of pg-boss generating a uuid.

Without being able to set IDs ourselves, we currently have to maintain a separate table to map IDs.

[timgit]

This would be a good option to send(). You can use insert([jobs]) for now, however.

[jorinvo]

Thanks @timgit! insert() does what we need. And thank you for the work on this lib :)

[nuelsoft]

Hello @timgit, thank you for the pointer. I was more worried by this

pg-boss/src/plans.js

Line 138 in 64df1e4

id uuid primary key not null default gen_random_uuid(),

It would be nice to maybe drop the type from uuid to a more flexible string.

Thanks again.