Tim Jones
Tim Jones
Yes, I think the completed jobs don't exist. Completed jobs are opt-in via the option `onComplete: true` from `send()`. When they're in the table, they will have the prefix `__state__completed__`
Thanks for the feedback. In regards to "fetch" semantics, I agree naming things is one of the hardest problems in computer science. Do you think "receive" like SQS has is...
This should hopefully be resolved in the next semver major (v10), which will kill off completion jobs in favor of dead letter queues.
No work is being planned for this request right now. There is a reason SQS doesn't allow you to hold on to a message for hours, first of all. But...
I'll consider adding this into v10
That's correct. schedule() overwrites any previous schedule for the specified queue.
You can use the startAfter property to schedule jobs.
My original hesitation with advisory locks is that they will cause a problem if created during job fetch time. However, I think if you were to configure them to only...
The job payload is jsonb. You could use data->>'userId', for example
This was not intended. It's an issue in the type definitions