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
I am sorry in advance if it is inappropriate to ask questions here. I was wondering if anyone could point me in the right direction to create this behavior:
Let's say I queue MyJob(param=123). I cannot re-queue MyJob(param=123) until it is executing(in-progress). (Behavior of until_executing). The edge case here is while MyJob(param=123) is executing, it should be able to queue again the same job, but it should wait until the first MyJob(param=123) is done before running the second instance with the same param.
According to the doc, there is a on_conflict: :reschedule, however it's not exactly this behavior I am looking for. The correct behavior would be :
:reject if job with same param is already queued
:reschedule if job with same param is running and there is not another one in the queue.
Thanks in advance :)
The text was updated successfully, but these errors were encountered:
Repository owner
locked and limited conversation to collaborators
Nov 15, 2021
Hi,
I am sorry in advance if it is inappropriate to ask questions here. I was wondering if anyone could point me in the right direction to create this behavior:
Let's say I queue MyJob(param=123). I cannot re-queue MyJob(param=123) until it is executing(in-progress). (Behavior of until_executing). The edge case here is while MyJob(param=123) is executing, it should be able to queue again the same job, but it should wait until the first MyJob(param=123) is done before running the second instance with the same param.
According to the doc, there is a on_conflict: :reschedule, however it's not exactly this behavior I am looking for. The correct behavior would be :
:reject if job with same param is already queued
:reschedule if job with same param is running and there is not another one in the queue.
Thanks in advance :)
The text was updated successfully, but these errors were encountered: