This might be a lack of comprehension from the docs, but I'm trying to understand what the pattern for dead letter handling is in river. My understanding is that if a job is an error state that it is eventually cancelled after exhausting retries. Once a job is cancelled it will eventually be cleaned from the database. What's the preferred pattern for moving the jobs to the side on error and then explicitly queuing again?
This might be a lack of comprehension from the docs, but I'm trying to understand what the pattern for dead letter handling is in river. My understanding is that if a job is an error state that it is eventually cancelled after exhausting retries. Once a job is cancelled it will eventually be cleaned from the database. What's the preferred pattern for moving the jobs to the side on error and then explicitly queuing again?