You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
arq supports this via custom job ids, see see arq.connections.ArqRedis.enqueue_job(). It guarantees that a job with a particular ID cannot be enqueued again until its execution has finished.
Which seems to imply that once a job has finished its execution, a new job with the same ID can be enqueued. But this is not true. If the job has result (return value, traceback information, etc.) left in Redis, new job with the same ID cannot be enqueued, see these lines of code. In this case the value of keep_result when initialize the worker would affect time duration of this conflict.
I think it's better to mention this in the Job uniqueness section.
The text was updated successfully, but these errors were encountered:
The doc says:
Which seems to imply that once a job has finished its execution, a new job with the same ID can be enqueued. But this is not true. If the job has result (return value, traceback information, etc.) left in Redis, new job with the same ID cannot be enqueued, see these lines of code. In this case the value of
keep_result
when initialize the worker would affect time duration of this conflict.I think it's better to mention this in the
Job uniqueness
section.The text was updated successfully, but these errors were encountered: